Loading ...
Sorry, an error occurred while loading the content.

Re: VIM on Mac OS X

Expand Messages
  • Ken Scott
    ... I have not been able to build a functioning gvim for Mac OS X either. I am hopeful that the Carbon version will start behaving for me. Ken --
    Message 1 of 14 , Oct 18, 2001
    • 0 Attachment
      on 10/16/01 5:25pm, gmark@... at gmark@... wrote:

      >
      > On Tuesday, October 16, 2001, at 12:17 AM, Eugene Lee wrote:
      >
      >> On Mon, Oct 15, 2001 at 10:13:02PM -0400, Benji Fisher wrote:
      >> :
      >> : Eugene Lee wrote:
      >> : >
      >> : > On Mon, Oct 15, 2001 at 01:09:30PM -0400, david craig wrote:
      >> : > :
      >> : > : I'd like vim available in terminal. Any guidance would be
      >> appreciated.
      >>
      > I must be missing something. I've been using it in terminal, but haven't
      > been able to get an OSX-native desktop icon VIM.
      >

      I have not been able to build a functioning gvim for Mac OS X either. I am
      hopeful that the Carbon version will start behaving for me.

      Ken

      --
      <>< Ken Scott ken@... http://www.pcisys.net/~kscott

      This is the day that the Lord has made;
      Let us rejoice and be glad in it -- Psalm 118:24
    • Eugene Lee
      ... Gvim is an X11 app. It runs fine if you have XFree86 and XDarwin installed. But this is not the same thing as a Cocoa/Carbon app that runs native on OS
      Message 2 of 14 , Oct 18, 2001
      • 0 Attachment
        On Thu, Oct 18, 2001 at 06:00:58PM -0600, Ken Scott wrote:
        :
        : on 10/16/01 5:25pm, gmark@... at gmark@... wrote:
        : >
        : > I must be missing something. I've been using it in terminal, but
        : > haven't been able to get an OSX-native desktop icon VIM.
        :
        : I have not been able to build a functioning gvim for Mac OS X either.
        : I am hopeful that the Carbon version will start behaving for me.

        Gvim is an X11 app. It runs fine if you have XFree86 and XDarwin
        installed. But this is not the same thing as a Cocoa/Carbon app that
        runs native on OS X's windowing system (Quartz), has its own icon, etc.


        --
        Eugene Lee
        eugene@...
      • Benji Fisher
        ... Here is a modification of Eugene Lee s instructions. The main changes are to the method of applying patches (which still gives some warning messages, I am
        Message 3 of 14 , Oct 25, 2001
        • 0 Attachment
          Eugene Lee wrote:
          >
          > On Mon, Oct 15, 2001 at 01:09:30PM -0400, david craig wrote:
          > :
          > : I'd like vim available in terminal. Any guidance would be appreciated.
          > : This is separate (or is it?) from a carbonized version of MacVIM.

          Here is a modification of Eugene Lee's instructions. The main changes
          are to the method of applying patches (which still gives some warning
          messages, I am not sure why) and using the default shell (tcsh)

          0) making a working directory

          $ mkdir vim-work
          $ cd vim-work

          1) download the source

          $ curl -O ftp://ftp.us.vim.org/pub/vim/unix/vim-6.0-rt1.tar.gz
          $ curl -O ftp://ftp.us.vim.org/pub/vim/unix/vim-6.0-rt2.tar.gz
          $ curl -O ftp://ftp.us.vim.org/pub/vim/unix/vim-6.0-src1.tar.gz
          $ curl -O ftp://ftp.us.vim.org/pub/vim/unix/vim-6.0-src2.tar.gz

          I used

          $ ftp ftp.rge.com
          ftp> cd pub/editors/vim/unix
          ftp> mget vim-6.0*

          Next time, I will get the bzipped version: just one file, and smaller
          total size. You can get bzip2 from
          http://www.entropy.ch/software/macosx/welcome.html
          (and also a pre-compiled terminal version of vim).

          2) unpack the files:

          $ gnutar zxf vim-6.0-rt1.tar.gz
          $ gnutar zxf vim-6.0-rt2.tar.gz
          $ gnutar zxf vim-6.0-src1.tar.gz
          $ gnutar zxf vim-6.0-src2.tar.gz

          3) download the patches

          $ for a in `jot -w%03d 11`; do curl -O
          ftp://ftp.us.vim.org/pub/vim/patches/6.0.${a}; done

          That looks like bourne syntax; I used ftp again, hitting <Enter> a couple
          of dozen times...

          4) apply the patches

          $ cd vim60
          $ for a in `jot -w%03d 11`; do patch -p1 < ../6.0.${a}; done

          I think that should be -p2. In tcsh,

          % gunzip 6.0*gz
          % cd vim60
          % foreach a (../6.0*)
          foreach -> patch -p2 <${a}
          foreach -> end

          5) build and install

          $ ./configure
          $ make
          $ sudo make install

          This works like a charm.

          --Benji Fisher
        • Eugene Lee
          ... I didn t use the interactive FTP method, because I don t know how many people actually know how to use the command-line FTP client. ... The 11 needs to
          Message 4 of 14 , Oct 25, 2001
          • 0 Attachment
            On Thu, Oct 25, 2001 at 09:38:52AM -0400, Benji Fisher wrote:
            :
            : 1) download the source
            :
            : $ curl -O ftp://ftp.us.vim.org/pub/vim/unix/vim-6.0-rt1.tar.gz
            : $ curl -O ftp://ftp.us.vim.org/pub/vim/unix/vim-6.0-rt2.tar.gz
            : $ curl -O ftp://ftp.us.vim.org/pub/vim/unix/vim-6.0-src1.tar.gz
            : $ curl -O ftp://ftp.us.vim.org/pub/vim/unix/vim-6.0-src2.tar.gz
            :
            : I used
            :
            : $ ftp ftp.rge.com
            : ftp> cd pub/editors/vim/unix
            : ftp> mget vim-6.0*

            I didn't use the interactive FTP method, because I don't know how many
            people actually know how to use the command-line FTP client.

            : 3) download the patches
            :
            : $ for a in `jot -w%03d 11`; do curl -O
            : ftp://ftp.us.vim.org/pub/vim/patches/6.0.${a}; done

            The "11" needs to be corrected to "27" (that's how many patches there
            are now :).

            : That looks like bourne syntax; I used ftp again, hitting <Enter> a couple
            : of dozen times...

            If folks are willing to use the command-line FTP client, forget jot!

            $ ftp ftp.us.vim.org
            ftp> cd pub/editors/vim/patches
            ftp> mget 6.0.*

            : 4) apply the patches
            :
            : $ cd vim60
            : $ for a in `jot -w%03d 11`; do patch -p1 < ../6.0.${a}; done

            Or forget jot again!

            $ cd vim60
            $ for a in ../6.0.*; do patch -p1 < ${a}; done


            --
            Eugene Lee
            eugene@...
          • Benji Fisher
            ... [snip] ... I still think it should be -p2. Maybe I am wrong: yesterday was my first experience using the patch program, and I had to spend some time with
            Message 5 of 14 , Oct 25, 2001
            • 0 Attachment
              Eugene Lee wrote:
              >
              [snip]
              > : 4) apply the patches
              > :
              > : $ cd vim60
              > : $ for a in `jot -w%03d 11`; do patch -p1 < ../6.0.${a}; done
              >
              > Or forget jot again!
              >
              > $ cd vim60
              > $ for a in ../6.0.*; do patch -p1 < ${a}; done

              I still think it should be -p2. Maybe I am wrong: yesterday was my
              first experience using the patch program, and I had to spend some time with
              "man patch". Here are the relevant lines from patch 6.0.002:

              *** ../vim60.1/src/option.c Wed Sep 26 16:25:52 2001
              --- src/option.c Thu Sep 27 09:44:40 2001

              If we already did "cd vim60" then I think we want to use -p2, effectively
              changing "../vim60.1/src/option.c" to "src/option.c" right? Since the patches
              use directories like vim60.1, it is not convenient to apply them from the
              parent of the vim60 directory.

              --Benji Fisher
            • Eugene Lee
              ... The README in the patches directory suggests this: Before patching, change to the top Vim directory, where the src and runtime directories are located.
              Message 6 of 14 , Oct 25, 2001
              • 0 Attachment
                On Thu, Oct 25, 2001 at 02:24:08PM -0400, Benji Fisher wrote:
                :
                : Eugene Lee wrote:
                : >
                : > $ cd vim60
                : > $ for a in ../6.0.*; do patch -p1 < ${a}; done
                :
                : I still think it should be -p2.

                The README in the patches directory suggests this:

                Before patching, change to the top Vim directory, where the "src"
                and "runtime" directories are located.
                Depending on the version of "patch" that you use, you may have add
                an argument to make it patch the right file:
                patch -p < 5.5.001
                patch -p0 < 5.5.001

                BTW, I never follow the vim60/vim60.1/etc. convention of renaming the
                top-level Vim directory. I always find it more confusing. :)


                --
                Eugene Lee
                eugene@...
              • Ken Scott
                ... FWIW, I ve always done patch -p0
                Message 7 of 14 , Oct 25, 2001
                • 0 Attachment
                  On Thu, 25 Oct 2001, Eugene Lee wrote:

                  > On Thu, Oct 25, 2001 at 02:24:08PM -0400, Benji Fisher wrote:
                  > :
                  > : Eugene Lee wrote:
                  > : >
                  > : > $ cd vim60
                  > : > $ for a in ../6.0.*; do patch -p1 < ${a}; done
                  > :
                  > : I still think it should be -p2.
                  >
                  > The README in the patches directory suggests this:
                  >
                  > Before patching, change to the top Vim directory, where the "src"
                  > and "runtime" directories are located.
                  > Depending on the version of "patch" that you use, you may have add
                  > an argument to make it patch the right file:
                  > patch -p < 5.5.001
                  > patch -p0 < 5.5.001
                  >
                  > BTW, I never follow the vim60/vim60.1/etc. convention of renaming the
                  > top-level Vim directory. I always find it more confusing. :)
                  >

                  FWIW, I've always done "patch -p0 < blah" from the top level vim directory
                  (vim60 these days) and have never had a problem.

                  Thanks for the for snippet to apply patches. I hadn't gotten around to
                  figuring out that part yet, and it will make it goe much faster now.

                  Ken


                  --
                  ><> Ken Scott kscott@... http://www.pcisys.net/~kscott

                  This is the day that the Lord has made;
                  I will rejoice and be glad in it! -- Psalm 118:24
                Your message has been successfully submitted and would be delivered to recipients shortly.