Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 2 Oct 2001 16:13:46 -0400 (EDT)
From:      David Scheidt <rufus@brain.mics.net>
To:        Rahul Siddharthan <rsidd@physics.iisc.ernet.in>
Cc:        j mckitrick <jcm@FreeBSD-uk.eu.org>, "Gary W. Swearingen" <swear@blarg.net>, freebsd-chat@FreeBSD.ORG
Subject:   Re: code density vs readability
Message-ID:  <Pine.BSI.4.20.0110021606080.7990-100000@brain.mics.net>
In-Reply-To: <20011002213051.A28111@lpt.ens.fr>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2 Oct 2001, Rahul Siddharthan wrote:

> j mckitrick said on Oct  2, 2001 at 19:59:56:
> > Interesting.  I know one guy who uses nvi just because of the license.
> > I must admit I like the multiple buffer and screen support.  I never
> > could get vim to do that in regular console mode.  Why do you detest it?
> 
> Oh, probably because I was used to vim, I admit...
> 
> That apart, I found vim's "multiple undo" scheme much more sensible
> than nvi's.  (u for undo, repeatedly if desired, ^R for redo.  Also
> more compatible with "traditional vi" where u is always undo, but once

Bull feathers!  That's entirely unlike real vi.  That's u undoes, and u 
again redoes the changes.  That's a huge finger macro breakage; I pretty
often flip back and forth between changed and unchanged versions (dozens of
times a day).   nvi's multiple undo with . is completely in line with how
vi works.

> only.)  But my big plus for vim is its paragraph-level operations, eg
> gqap for formatting a paragraph.  Not a big deal with programs, but a
> huge help with text and emails, and even handles quoted email
> correctly and is great at unmangling Outlook-generated mail.  I don't
> think nvi has that; traditional vi doesn't.
> 

I'm not convinced this needs to be part of the editor.  Checkout par
(ports/textproc/par), I think it does everything vim does. 


> For programs, I like its syntax highlighting.  I don't know whether
> nvi has that.

I hope not...
> 
> And I think vim does handle multiple buffers in console mode.  I
> haven't investigated it, when doing "serious" work I'm always running
> X and I just find it easier to open two xterms...

vim does do multiple buffers.  


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-chat" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.4.20.0110021606080.7990-100000>