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

Re: Vim (Vi IMproved) for Mac OSX ( was Re: Vim on Mac OS 10.2 )

Expand Messages
  • Benji Fisher
    ... 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. When I get around to updating the
    Message 1 of 12 , Aug 28, 2002
    • 0 Attachment
      ewitness - Ben Fowler wrote:
      >
      > I realise that it is a little unfair for me to ask for something that
      > I can't volunteer to help with, but could the page you mention (which
      > is the central page for MacVim) possibly have a note as to whether we
      > should be using the suggested makefile, or Project Builder. Perhaps an
      > answer to the question: Why not just switch over to Project Builder?

      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." When I get around to updating the
      web page, I will try to remember to add a note on make vs. PB. If you do not
      see it by the end of next week, feel free to send me a reminder.

      > I am having some problems with <CR>, for example, this mapping
      >
      > n <D-n> :confirm enew<CR>
      >
      > exists, but the whole command including the literal <CR> is printed.
      > I suspect that it would work better if the <CR> was interpreted
      > as the keystroke carriage return.
      >
      > I enclose a copy of my current settings (bug report) and a small
      > patch.
      >

      This works for me (using the 6.1.141 that I posted). What version are you
      using? OS 10.1 or 10.2? (I hate having to ask that!) From your bug report, it
      looks as though you are running in 'compatible' mode: in particular, your
      'compatible' option includes the "<" flag. I'll have to think about adjusting
      the system vimrc/gvimrc files to deal with this. For example, can I get the
      <D-n> map to work without a heavy-handed ":set nocp"?

      > Also, I can't get the cursor arrow keys to work in colon mode.

      Let's hope that is the same problem.

      > Do you need any help with MacVim.

      Sure. What do you want to do: work on the source, maintain the web site,
      ... ? Please re-send your patch (preferably in the body of the mail, not as an
      attachment) to the list, with an explanation of what it is supposed to do.

      HTH --Benji Fisher
    • ewitness - Ben Fowler
      ... It is the page that google leads one to, and is nicely laid out and concise. ... 10.1.5 . I think that you are right, and it is documented that cpoptions
      Message 2 of 12 , Aug 28, 2002
      • 0 Attachment
        At 9:45 am -0400 28/8/02, Benji Fisher wrote:
        >ewitness - Ben Fowler wrote:
        >>
        >> I realise that it is a little unfair for me to ask for something that
        >> I can't volunteer to help with, but could the page you mention (which
        >> is the central page for MacVim) possibly have a note as to whether we
        >> should be using the suggested makefile, or Project Builder. Perhaps an
        >> answer to the question: Why not just switch over to Project Builder?
        >
        > 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 am having some problems with <CR>, for example, this mapping
        > >
        > > n <D-n> :confirm enew<CR>
        >>
        > > exists, but the whole command including the literal <CR> is printed. ...
        >
        > This works for me (using the 6.1.141 that I posted). What version are you
        >using? OS 10.1 or 10.2? (I hate having to ask that!) From your bug report, it
        >looks as though you are running in 'compatible' mode: in particular, your
        >'compatible' option includes the "<" flag. I'll have to think about adjusting
        >the system vimrc/gvimrc files to deal with this. For example, can I get the
        ><D-n> map to work without a heavy-handed ":set nocp"?

        10.1.5 .

        I think that you are right, and it is documented that cpoptions must
        not contain <, so that <CR> is interpreted rather than taken literally.
        I did try this.

        I suspect that I am running in compatibiliy mode.

        If I type :set nocp then I get the arrow keys working; but even
        sourcing menu.vim does not get the menus/Apple keys to do other than
        I described.

        However. If I source gvimrc, apart from an error on line 94
        (no menu of that name), this does fix at least the basics:
        File/New, File/Open ...

        If my reading of the documentation of the docs is correct, then
        the first step in initialisation is reading $VIM/menu.vim ;
        in which case, this file ought to have the :set nocp at its head.

        > > Also, I can't get the cursor arrow keys to work in colon mode.
        >
        > Let's hope that is the same problem.

        As I say. It looks like it.

        > > Do you need any help with MacVim.
        >
        > Sure. What do you want to do: work on the source, maintain the web site,
        >... ? Please re-send your patch (preferably in the body of the mail, not as an
        >attachment) to the list, with an explanation of what it is supposed to do.

        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.

        Patches

        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

        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)

        Index: gui_mac.c
        ===================================================================
        RCS file: /cvsroot/vim/vim/src/gui_mac.c,v
        retrieving revision 1.37
        diff -c -r1.37 gui_mac.c
        *** gui_mac.c 13 Jun 2002 18:59:43 -0000 1.37
        --- gui_mac.c 27 Aug 2002 15:28:02 -0000
        ***************
        *** 93,100 ****
        --- 93,102 ----
        /* Include some file. TODO: move into os_mac.h */
        #include <Menus.h>
        #include <Resources.h>
        + #if !__APPLE__
        #include <StandardFile.h>
        #include <Traps.h>
        + #endif
        #include <Balloons.h>
        #include <Processes.h>
        #ifdef USE_AEVENT
        ***************
        *** 3136,3143 ****
        r = hex_digit(name[1]) * 16 + hex_digit(name[2]);
        g = hex_digit(name[3]) * 16 + hex_digit(name[4]);
        b = hex_digit(name[5]) * 16 + hex_digit(name[6]);
        if (r < 0 || g < 0 || b < 0)
        ! return INVALCOLOR;
        return RGB(r, g, b);
        }
        else
        --- 3138,3147 ----
        r = hex_digit(name[1]) * 16 + hex_digit(name[2]);
        g = hex_digit(name[3]) * 16 + hex_digit(name[4]);
        b = hex_digit(name[5]) * 16 + hex_digit(name[6]);
        + /*
        + unsigned short cannot be < 0
        if (r < 0 || g < 0 || b < 0)
        ! return INVALCOLOR; */
        return RGB(r, g, b);
        }
        else
        ***************
        *** 4646,4660 ****
        GrafPtr oldPort;
        short itemHit;
        char_u *buttonChar;
        ! char_u *messageChar;
        Rect box;
        short button;
        short lastButton;
        short itemType;
        short useIcon;
        ! short lenght;
        short width;
        ! short height;
        short totalButtonWidth = 0; /* the width of all button together incuding spacing */
        short widestButton = 0;
        short dfltButtonEdge = 20; /* gut feeling */
        --- 4650,4664 ----
        GrafPtr oldPort;
        short itemHit;
        char_u *buttonChar;
        ! /* char_u *messageChar; */
        Rect box;
        short button;
        short lastButton;
        short itemType;
        short useIcon;
        ! /* short length; BPF unused */
        short width;
        ! /* short height; BPF unused */
        short totalButtonWidth = 0; /* the width of all button together incuding spacing */
        short widestButton = 0;
        short dfltButtonEdge = 20; /* gut feeling */
        ***************
        *** 5188,5203 ****
        */

        CInfoPBRec theCPB;
        ! Str255 directoryName;
        ! char_u temporary[255];
        ! /* char filename[255]; */
        char_u fname[256];
        ! char_u *temporaryPtr = temporary;
        char_u *filenamePtr = fname;
        OSErr error;
        int folder = 1;
        #ifdef USE_UNIXFILENAME
        ! char *p;
        SInt16 dfltVol_vRefNum;
        SInt32 dfltVol_dirID;
        FSRef refFile;
        --- 5192,5207 ----
        */

        CInfoPBRec theCPB;
        ! /* Str255 directoryName; BPF unused */
        ! /* char_u temporary[255]; BPF unused */
        ! /* char filename[255]; */
        char_u fname[256];
        ! /* char_u *temporaryPtr = temporary; BPF unused */
        char_u *filenamePtr = fname;
        OSErr error;
        int folder = 1;
        #ifdef USE_UNIXFILENAME
        ! /* char *p; BPF unused */
        SInt16 dfltVol_vRefNum;
        SInt32 dfltVol_dirID;
        FSRef refFile;

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

        Index: term.c
        ===================================================================
        RCS file: /cvsroot/vim/vim/src/term.c,v
        retrieving revision 1.53
        diff -c -r1.53 term.c
        *** term.c 15 Mar 2002 22:05:01 -0000 1.53
        --- term.c 27 Aug 2002 15:28:07 -0000
        ***************
        *** 1372,1378 ****
        # define DEFAULT_TERM (char_u *)"pcterm"
        #endif

        ! #if defined(UNIX) && !defined(__MINT__)
        # define DEFAULT_TERM (char_u *)"ansi"
        #endif

        --- 1372,1378 ----
        # define DEFAULT_TERM (char_u *)"pcterm"
        #endif

        ! #if defined(UNIX) && !defined(__MINT__) && !defined(MACOS)
        # define DEFAULT_TERM (char_u *)"ansi"
        #endif

        There are a handful of other minor fixes that I have put into
        my sources, but have not passed on here to avoid mistakes and/
        or misconceptions.

        I have just compiled Vim and started it the mod to menu.vim and
        all is well.

        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
      • 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 3 of 12 , Aug 29, 2002
        • 0 Attachment
          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 4 of 12 , Aug 31, 2002
          • 0 Attachment
            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 5 of 12 , Sep 2 6:34 PM
            • 0 Attachment
              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 6 of 12 , Sep 14 8:09 PM
              • 0 Attachment
                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 7 of 12 , Sep 16 5:28 AM
                • 0 Attachment
                  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 8 of 12 , Sep 16 5:42 AM
                  • 0 Attachment
                    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 9 of 12 , Sep 16 6:14 AM
                    • 0 Attachment
                      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 10 of 12 , Sep 16 8:09 AM
                      • 0 Attachment
                        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 11 of 12 , Sep 16 8:28 AM
                        • 0 Attachment
                          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 12 of 12 , Sep 16 8:54 AM
                          • 0 Attachment
                            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.