cvs commit: src/release/scripts print-cdrom-packages.sh

[Gary Jennejohn]

"David O'Brien" writes:
> On Fri, Dec 05, 2003 at 12:59:00AM +0100, Gary Jennejohn wrote:
> > "Brian F. Feldman" writes:
> > > Andreas Klemm <andreas at FreeBSD.org> wrote:
> > > > BTW, robert, if you already think of terms to "waste" time
> > > > for loadable editor modules ... the only thing I'm really
> > > > missing in standard vi is an extended command line with
> > > > - history function
> > > > - save history and
> > > > - editable like everything other compiled and linked with readline lib.
> ...
> > > I don't think it would be exactly the most trivial thing to give nvi 
> > > vi-command-history, but it's certainly worth doing.  It doesn't use 
> ...
> > (x)vile already has functionality to edit thiings like search patterns
> > and file names (using the arrow keys to move around). It also keeps
> > track of quite a few of the last search patterns and allows scrolling
> > through them using the arrow keys.
> 
> Vim has all this, that's how it got as big as it is -- people make lists
> like the above and the Vim author responds.  So if we're going to import
> [x]vile, we should import Vim instead as its got a larger FreeBSD
> userbase.
> 
> That said, I don't see us importing any 'vi' clones, so why is another
> editor to import being suggested?
> 

I wasn't suggesting importing another editor but rather pointing out
that, if one desires the ability to edit previous input, there are already
existing editors which can do that in ports so why modify nvi?

IMO nvi is more than good enough as it is for the base system.

---
Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org gj[at]denx.de