From: peter (Peter da Silva) Date: 00:04 on 05 Jan 2004 Subject: Panther. Again. AUGH. They replaced the perfectly good "nvi" in Jaguar with one of those inadequate and incomplete clones (to be precise, "vim"). This is intolerable. (no, I'm not going to try and quantify exactly why vim sucks, suffice it to say that I've been using "vi" longer than the Macintosh has existed, and vim breaks my finger macros)
From: Aaron J. Grier Date: 06:34 on 07 Jan 2004 Subject: Re: Panther. Again. On Sun, Jan 04, 2004 at 06:04:51PM -0600, Peter da Silva wrote: > (no, I'm not going to try and quantify exactly why vim sucks, suffice > it to say that I've been using "vi" longer than the Macintosh has > existed, and vim breaks my finger macros) echo "set nocp" >> ~/.vimrc or am I missing something not so obvious?
From: Aaron J. Grier Date: 06:40 on 07 Jan 2004 Subject: Re: Panther. Again. On Tue, Jan 06, 2004 at 10:34:47PM -0800, Aaron J. Grier wrote: > echo "set nocp" >> ~/.vimrc err... "set cp" in your case, even. I do agree somewhat, though... if I want vim, I'll invoke vim. if I want vi, I'll invoke vi.
From: peter (Peter da Silva) Date: 13:03 on 07 Jan 2004 Subject: Re: Panther. Again. > echo "set nocp" >> ~/.vimrc > > or am I missing something not so obvious? I have no earthly idea. I haven't downgraded to Panther yet so I have no idea what exactly this "no compatibility" mode does, or why I would want to make vim less compatible with "vi" when I've got 20 years of "vi" use programmed into my fingers, or why you think it would help. Every few years this happens, someone tosses vim or gvim at me, and breaks down my resistence with "oh, they've fixed all the problems", and I spend a week trying to tweak it so it doesn't drive me totally batty if I try and use it for more than a few minutes, and I finally give up. My fingers are programmed with the rules of the real "vi". I hate Apple for forcing this on me again. If they're going to ship vim, why the hell couldn't they leave nvi in there as well? It's not like it takes up much space compared with "Expose" or "Windows XP Emulation" (AKA fast user switching, AKA why not do something different from Microsoft and make it real virtual consoles so I can be logged on more than once, you slimy beggars?).
From: Michael G Schwern Date: 06:16 on 14 Jan 2004 Subject: Re: Panther. Again. On Wed, Jan 07, 2004 at 07:03:47AM -0600, Peter da Silva wrote: > I have no earthly idea. I haven't downgraded to Panther yet so I > have no idea what exactly this "no compatibility" mode does, or > why I would want to make vim less compatible with "vi" when I've > got 20 years of "vi" use programmed into my fingers, or why you > think it would help. Because I like to be able to move the cursor even when I'm in an edit mode. But what do I know, I use xemacs.
From: peter (Peter da Silva) Date: 12:47 on 14 Jan 2004 Subject: Re: Panther. Again. > Because I like to be able to move the cursor even when I'm in an edit mode. VI doesn't have an "edit mode".
From: David Champion Date: 16:34 on 07 Jan 2004 Subject: Re: Panther. Again. * On 2004.01.07, in <20040107063447.GA19404@xxxxxxxxx.xxxxx.xxxx.xxx>, * "Aaron J. Grier" <agrier@xxxxxxxxx.xxx> wrote: > On Sun, Jan 04, 2004 at 06:04:51PM -0600, Peter da Silva wrote: > > (no, I'm not going to try and quantify exactly why vim sucks, suffice > > it to say that I've been using "vi" longer than the Macintosh has > > existed, and vim breaks my finger macros) > > echo "set nocp" >> ~/.vimrc > > or am I missing something not so obvious? Yes: compatibility mode isn't. Vim is vim, even when it's pretending to be vi, and it can't completely hide the sorry fact. Fortunately, I knew this was going to happen, and I'm keeping my old vi exec. I realize there are advantages in vim over other vi implementations, and maybe one day, when the inevitable comes round the bend, I'll become able to tolerate them. Until then, I wish that when I asked for vi, I got vi, and when I asked for viper, I got emacs.
Generated at 10:27 on 16 Apr 2008 by mariachi