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

Re: Vim (Vi IMproved) for Mac OSX

Expand Messages
  • Benji Fisher
    ... I ll take that (both parts) as a compliment: thanks! [snip some items still on my TODO list...] ... I think we are pretty close. :) Have you looked at my
    Message 1 of 12 , Aug 29, 2002
      ewitness - Ben Fowler wrote:
      >
      > At 9:45 am -0400 28/8/02, Benji Fisher wrote:
      > > As of now, I am the only one taking advantage of this web space, so I
      > >would not call it the "central page for MacVim."
      >
      > It is the page that google leads one to, and is nicely laid out and concise.

      I'll take that (both parts) as a compliment: thanks!

      [snip some items still on my TODO list...]

      > > > Do you need any help with MacVim.
      >
      > I had in mind working on the source. My objective, without being unkind
      > to the fine folk at BareBones would be to make Vim the best text editor
      > on Mac OS X, the best text editor on any BSD platform, and the only text
      > editor your would ever need.

      I think we are pretty close. :) Have you looked at my bug list at
      http://macvim.swdev.org/OSX/#Bugs ? Briefly,

      1. dialogue boxes
      2. forking
      3. "Hit Enter" when starting vim with drag-and-drop
      4. keyboard shortcuts in :menu

      The details are not entirely up to date (sorry): for 1, the patch to disable
      dialogue boxes (better than crashing!) became official at some point; I think
      someone sent a patch for 3 that I have not tried yet. AFAIK none of these (with
      the possible exception of 3) has been completely resolved.

      --Benji Fisher
    • Rain Dog
      ... How about this: o cvs -d:pserver:anonymous@cvs.vim.sourceforge.net:/cvsroot/vim login o At the CVS password: prompt, press Return. o cvs -z3
      Message 2 of 12 , Aug 31, 2002
        Benji Fisher wrote:

        > several of the official (numbered) patches are Mac-specific, so I
        > would try patching the sources before compiling. You might prefer
        > to use CVS to
        > download the patched source. (Can someone contribute an
        > OSX-specific HOWTO for
        > downloading by CVS? I could add that to the web site.)

        How about this:

        o cvs -d:pserver:anonymous@...:/cvsroot/vim login
        o At the "CVS password:" prompt, press Return.
        o cvs -z3
        -d:pserver:anonymous@...:/cvsroot/vim co vim
        o cd ./vim/src/
        o open os_mac.rsr.hqx
        (launches StuffIt Expander to extract gui_mac.rsrc)

        Then, either

        o pbxbuild

        or

        o curl http://macvim.swdev.org/OSX/files/Make_osx.mak > Make_osx.mak
        o make -f Make_osx.mak
        (I actually use "env IME=no make -f Make_osx.mak", because I get the
        "Undefined symbol: _GetACP" link error with the Input Method
        extensions.)

        Finally,

        o Periodically run "cvs update -d" from the vim/ directory to
        bring your
        copy of the source files up to date with the repository.

        > Have you looked at my bug list at http://macvim.swdev.org/OSX/#Bugs ?
        > Briefly,
        >
        > 1. dialogue boxes
        > 2. forking
        > 3. "Hit Enter" when starting vim with drag-and-drop
        > 4. keyboard shortcuts in :menu
        >
        > The details are not entirely up to date (sorry): for 1, the patch
        > to disable
        > dialogue boxes (better than crashing!) became official at some point

        Did the patches I posted the other day not resolve the dialog box
        issues?
        (You'll need to reenable dialog boxes, of course.)

        Peter
      • Benji Fisher
        ... Thanks, I ll give it a try and post it if it works for me. ... Sorry, that is one of the patches I have not had time to try. (I have been on vacation, and
        Message 3 of 12 , Sep 2, 2002
          Rain Dog wrote:
          >
          > Benji Fisher wrote:
          > (Can someone contribute an
          > > OSX-specific HOWTO for
          > > downloading by CVS? I could add that to the web site.)
          >
          > How about this:
          >
          > o cvs -d:pserver:anonymous@...:/cvsroot/vim login
          > o At the "CVS password:" prompt, press Return.
          > o cvs -z3
          > -d:pserver:anonymous@...:/cvsroot/vim co vim
          > o cd ./vim/src/
          > o open os_mac.rsr.hqx
          > (launches StuffIt Expander to extract gui_mac.rsrc)
          >
          > Then, either
          >
          > o pbxbuild
          >
          > or
          >
          > o curl http://macvim.swdev.org/OSX/files/Make_osx.mak > Make_osx.mak
          > o make -f Make_osx.mak
          > (I actually use "env IME=no make -f Make_osx.mak", because I get the
          > "Undefined symbol: _GetACP" link error with the Input Method
          > extensions.)
          >
          > Finally,
          >
          > o Periodically run "cvs update -d" from the vim/ directory to
          > bring your
          > copy of the source files up to date with the repository.

          Thanks, I'll give it a try and post it if it works for me.

          > > Have you looked at my bug list at http://macvim.swdev.org/OSX/#Bugs ?
          > > Briefly,
          > >
          > > 1. dialogue boxes
          > > 2. forking
          > > 3. "Hit Enter" when starting vim with drag-and-drop
          > > 4. keyboard shortcuts in :menu
          > >
          > > The details are not entirely up to date (sorry): for 1, the patch
          > > to disable
          > > dialogue boxes (better than crashing!) became official at some point
          >
          > Did the patches I posted the other day not resolve the dialog box
          > issues?
          > (You'll need to reenable dialog boxes, of course.)

          Sorry, that is one of the patches I have not had time to try. (I have been
          on vacation, and kept busy when I got back with the vim users' list.) I will
          try to test all the patches sent to this list soon, perhaps this week.

          If (1) and (3) above have been solved, then (2) is the most important
          IMHO. The problem is that, for now, we cannot start vim (with the Aqua GUI)
          from the command line properly. We can use the open command, but then we cannot
          pass any command-line arguments. This is important for communication with
          external programs: for example, a TeX previewer wants to start vim with a file
          name and a particular line. We can start the vim binary directly, and give it
          the -g (GUI) flag, but the failure to fork means that it comes up in the
          background (ugh).

          Another item for the list: figure out how to get a single binary that will
          work on OSX 10.1.x and 10.2.

          --Benji Fisher
        • Benji Fisher
          ... This file does not exist in the standard distribution: I assume it gets added by CVS. Maybe this change can be implemented by the CVS maintainers. ...
          Message 4 of 12 , Sep 14, 2002
            On Wednesday, August 28, 2002, at 11:37 AM, ewitness - Ben Fowler wrote:

            > [snip]
            > 1. cvsignore to include .DS_Store (Finder's view settings).
            >
            > diff -c -r1.2 .cvsignore
            > *** .cvsignore 13 Nov 2001 08:01:56 -0000 1.2
            > --- .cvsignore 27 Aug 2002 15:27:54 -0000
            > ***************
            > *** 1,4 ****
            > ! objects
            > ! vim
            > ObjC
            > ObjGO
            > --- 1,6 ----
            > ! .DS_Store
            > ObjC
            > ObjGO
            > + build
            > + objects
            > + vim

            This file does not exist in the standard distribution: I assume it
            gets added by CVS. Maybe this change can be implemented by the CVS
            maintainers.

            > 2. gui_mac.c
            > a) Don't include Classic only headers (may need to modify this in due
            > course.
            > b) Remove superfluous arithmetic comparison on pixelvalues
            > c) Remove references to several unused variables (I may have been
            > a bit
            > over-enthusiastic there)
            [patch snipped]

            So far, no problems with this. I'll repackage the patch and post
            it on the web page soon.

            > 3. term.c Fix double definition of DEFAULT_TERM, which seems
            > to be best as 'ansi' but I could be wrong.

            We already discussed this: I would like it if we can fix it to
            make beos-ansi the default in non-GUI vim on OSX. Does this get used at
            all in the GUI version? I may try to produce a patch based on our
            previous discussion, but feel free to beat me to it! ;)

            --Benji Fisher
          • ewitness - Ben Fowler
            ... I hope 1) that I am not misleading you with this, and 2) not posting info to this list which is unduly bogus. I am working on the basis that there are
            Message 5 of 12 , Sep 16, 2002
              At 11:09 pm -0400 14/9/02, Benji Fisher wrote:
              >On Wednesday, August 28, 2002, at 11:37 AM, ewitness - Ben Fowler wrote:
              >
              >[ ... ]
              >
              >>3. term.c Fix double definition of DEFAULT_TERM, which seems
              >>to be best as 'ansi' but I could be wrong.
              >
              > We already discussed this: I would like it if we can fix it to make beos-ansi the default in non-GUI vim on OSX. Does this get used at all in the GUI version? I may try to produce a patch based on our previous discussion, but feel free to beat me to it! ;)

              I hope 1) that I am not misleading you with this, and 2) not posting
              info to this list which is unduly bogus.

              I am working on the basis that there are three versions of vim of
              interest to Mac OS X people:

              a) vim (runs in a standard tcsh terminal) and replaces the BSD vi
              b) gvim (built along with the above, and has an XDarwin gui)
              c) Vim (the Aqua/Carbon version).

              I build a) and c), but not b) as I am not running X. The term 'GUI version'
              might be ambiguous.

              In my hands, the DEFAULT_TERMINAL is set to ansi and is needed. I may be
              wrong about this, and it would explain why I had to add the curses functions.
              However, I would point out that even with guioptions 'gmrLtT', it is not
              possible to activate the Toolbar, and there is no choice of font.

              (Arguably, Vim should be developed so that it used the Quartz graphics
              model. I expect that currently it opens a text window and, well, draws
              plain text).

              I am not up on the details of the non-gui MacOS vim, but if it doesn't
              use ansi, whilst I can't promise to eat a hat, I would be prepared
              to decapitate dentally a jelly baby of a less favoured hue.

              My patch shouldn't do anything for the non-gui vim, in that case the
              DEFAULT_TERMINAL is selected by the straight-forward definition of
              MACOS, and no definition of UNIX.

              My patch is for the opposite case, id est when both MACOS and UNIX
              are defined.

              Ben.
              --
              Privileged/Confidential Information may be contained in this message.
              If you are not the addressee indicated in this message (or responsible
              for delivery of the message to such person), you may not copy or deliver
              this message to anyone. In such case, you should destroy this message
              and kindly notify the sender by reply email. Please advise immediately
              if you or your employer do not consent to Internet email messages of this
              kind. Opinions, conclusions and other information in this message that
              do not relate to the official business of ewitness Limited shall be
              understood as neither given nor endorsed by it.

              eWitness Limited, Alpha House, Redvers Close, Lawnswood Business Park, Leeds, LS16 6QY
              Telephone: 0113 2951112 Fax: 0113 2951114
            • ewitness - Ben Fowler
              ... I am not sure I understand all that. Looking at the repository, I can see the file that I have in mind, last modified 10 months ago. Here is my latest
              Message 6 of 12 , Sep 16, 2002
                At 11:09 pm -0400 14/9/02, Benji Fisher wrote:
                >On Wednesday, August 28, 2002, at 11:37 AM, ewitness - Ben Fowler wrote:
                >
                >>[snip]
                >>1. cvsignore to include .DS_Store (Finder's view settings).
                >>
                >>diff -c -r1.2 .cvsignore
                >>*** .cvsignore 13 Nov 2001 08:01:56 -0000 1.2
                >>--- .cvsignore 27 Aug 2002 15:27:54 -0000
                >>***************
                >>*** 1,4 ****
                >>! objects
                >>! vim
                >> ObjC
                >> ObjGO
                >>--- 1,6 ----
                >>! .DS_Store
                >> ObjC
                >> ObjGO
                >>+ build
                >>+ objects
                >>+ vim
                >
                > This file does not exist in the standard distribution: I assume it gets added by CVS. Maybe this change can be implemented by the CVS maintainers.

                I am not sure I understand all that. Looking at the repository, I can see
                the file that I have in mind, last modified 10 months ago. Here is my latest
                context diff.

                Index: src/.cvsignore
                ===================================================================
                RCS file: /cvsroot/vim/vim/src/.cvsignore,v
                retrieving revision 1.2
                diff -c -r1.2 .cvsignore
                *** src/.cvsignore 13 Nov 2001 08:01:56 -0000 1.2
                --- src/.cvsignore 16 Sep 2002 11:42:34 -0000
                ***************
                *** 1,4 ****
                ! objects
                ! vim
                ObjC
                ObjGO
                --- 1,8 ----
                ! *.swp
                ! .DS_Store
                ObjC
                ObjGO
                + build
                + gui_mac.rsrc
                + objects
                + vim

                Ben
                --
                Privileged/Confidential Information may be contained in this message.
                If you are not the addressee indicated in this message (or responsible
                for delivery of the message to such person), you may not copy or deliver
                this message to anyone. In such case, you should destroy this message
                and kindly notify the sender by reply email. Please advise immediately
                if you or your employer do not consent to Internet email messages of this
                kind. Opinions, conclusions and other information in this message that
                do not relate to the official business of ewitness Limited shall be
                understood as neither given nor endorsed by it.

                eWitness Limited, Alpha House, Redvers Close, Lawnswood Business Park, Leeds, LS16 6QY
                Telephone: 0113 2951112 Fax: 0113 2951114
              • Gregory Seidman
                ewitness - Ben Fowler sez: [...] } In my hands, the DEFAULT_TERMINAL is set to ansi and is needed. I may be } wrong about this, and it would explain why I had
                Message 7 of 12 , Sep 16, 2002
                  ewitness - Ben Fowler sez:
                  [...]
                  } In my hands, the DEFAULT_TERMINAL is set to ansi and is needed. I may be
                  } wrong about this, and it would explain why I had to add the curses functions.
                  } However, I would point out that even with guioptions 'gmrLtT', it is not
                  } possible to activate the Toolbar, and there is no choice of font.
                  }
                  } (Arguably, Vim should be developed so that it used the Quartz graphics
                  } model. I expect that currently it opens a text window and, well, draws
                  } plain text).
                  }
                  } I am not up on the details of the non-gui MacOS vim, but if it doesn't
                  } use ansi, whilst I can't promise to eat a hat, I would be prepared
                  } to decapitate dentally a jelly baby of a less favoured hue.

                  I have found that the vim terminal setting that works best for Terminal.app
                  is builtin_beos-ansi.

                  [...]
                  } Ben.
                  --Greg
                • Benji Fisher
                  ... When I say standard distribution I mean what you get by downloading files from ftp.vim.org . IIUC, you are looking at files on CVS, which include some
                  Message 8 of 12 , Sep 16, 2002
                    On Monday, September 16, 2002, at 08:42 AM, ewitness - Ben Fowler wrote:

                    > At 11:09 pm -0400 14/9/02, Benji Fisher wrote:
                    >> This file does not exist in the standard distribution: I assume
                    >> it gets added by CVS. Maybe this change can be implemented by the CVS
                    >> maintainers.
                    >
                    > I am not sure I understand all that. Looking at the repository, I can
                    > see
                    > the file that I have in mind, last modified 10 months ago. Here is my
                    > latest
                    > context diff.

                    When I say "standard distribution" I mean what you get by
                    downloading files from ftp.vim.org . IIUC, you are looking at files on
                    CVS, which include some (such as src/.cvsignore ) that do not exist in
                    the standard distribution.

                    --Benji Fisher
                  • ewitness - Ben Fowler
                    ... Yes. I am dealing with files in the CVS repository. (How else does one handle patches...)? Assuming that you don t think that modifyiny .cvsignore is worth
                    Message 9 of 12 , Sep 16, 2002
                      At 11:09 am -0400 16/9/02, Benji Fisher wrote:
                      >On Monday, September 16, 2002, at 08:42 AM, ewitness - Ben Fowler wrote:
                      >
                      >>At 11:09 pm -0400 14/9/02, Benji Fisher wrote:
                      >>> This file does not exist in the standard distribution: I assume it gets added by CVS. Maybe this change can be implemented by the CVS maintainers.
                      >>
                      >>I am not sure I understand all that. Looking at the repository, I can see
                      >>the file that I have in mind, last modified 10 months ago. Here is my latest
                      >>context diff.
                      >
                      > When I say "standard distribution" I mean what you get by downloading files from ftp.vim.org . IIUC, you are looking at files on CVS, which include some (such as src/.cvsignore ) that do not exist in the standard distribution.

                      Yes. I am dealing with files in the CVS repository. (How else does one
                      handle patches...)?

                      Assuming that you don't think that modifyiny .cvsignore is worth
                      doing, I shall no long er submite patches to it.

                      Ben.
                      --
                      Privileged/Confidential Information may be contained in this message.
                      If you are not the addressee indicated in this message (or responsible
                      for delivery of the message to such person), you may not copy or deliver
                      this message to anyone. In such case, you should destroy this message
                      and kindly notify the sender by reply email. Please advise immediately
                      if you or your employer do not consent to Internet email messages of this
                      kind. Opinions, conclusions and other information in this message that
                      do not relate to the official business of ewitness Limited shall be
                      understood as neither given nor endorsed by it.

                      eWitness Limited, Alpha House, Redvers Close, Lawnswood Business Park, Leeds, LS16 6QY
                      Telephone: 0113 2951112 Fax: 0113 2951114
                    • ewitness - Ben Fowler
                      ... Assuming that when you say Terminal.app, you mean the same as src/vim, then the DEFAULT_TERMINAL setting in term.c is dumb . If you want beos-ansi then
                      Message 10 of 12 , Sep 16, 2002
                        At 9:14 am -0400 16/9/02, Gregory Seidman wrote:
                        >ewitness - Ben Fowler sez:
                        >[...]
                        >} I am not up on the details of the non-gui MacOS vim, but if it doesn't
                        >} use ansi, whilst I can't promise to eat a hat, I would be prepared
                        >} to decapitate dentally a jelly baby of a less favoured hue.
                        >
                        >I have found that the vim terminal setting that works best for Terminal.app
                        >is builtin_beos-ansi.

                        Assuming that when you say Terminal.app, you mean the same as src/vim, then the
                        DEFAULT_TERMINAL setting in term.c is "dumb". If you want "beos-ansi" then
                        we need a patch to term.c to accomplish this.

                        Ben.

                        --
                        Privileged/Confidential Information may be contained in this message.
                        If you are not the addressee indicated in this message (or responsible
                        for delivery of the message to such person), you may not copy or deliver
                        this message to anyone. In such case, you should destroy this message
                        and kindly notify the sender by reply email. Please advise immediately
                        if you or your employer do not consent to Internet email messages of this
                        kind. Opinions, conclusions and other information in this message that
                        do not relate to the official business of ewitness Limited shall be
                        understood as neither given nor endorsed by it.

                        eWitness Limited, Alpha House, Redvers Close, Lawnswood Business Park, Leeds, LS16 6QY
                        Telephone: 0113 2951112 Fax: 0113 2951114
                      Your message has been successfully submitted and would be delivered to recipients shortly.