Re: Holy Cow -- What happened to bash / vi??

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Excerpts from Aaron Griffin's message of Mon Jun 22 12:27:01 -0400 2009:
> On Mon, Jun 22, 2009 at 7:02 AM, Daenyth Blank<daenyth+arch@xxxxxxxxx> wrote:
> > On Mon, Jun 22, 2009 at 07:47, Loui Chang<louipc.ist@xxxxxxxxx> wrote:
> >> On Mon 22 Jun 2009 03:09 -0500, David C. Rankin wrote:
> >>> I will downgrade vi. If that is what the future of vi looks like, I
> >>> don't want any part of it. Changes that dramatic ought to be forked.
> >>
> >> You were previously using vim named 'vi'.
> >> The new one is actually a fork of vi called nvi.
> >>
> >>
> >
> > I don't understand why anyone would use any vi. Use vim instead...
> 
> I've always harped on this point. I use "vim". Vim is the name of the
> application that I use. Vim just happens to be largely vi compatible,
> but I still use vim.

Yeah, I'm not a huge fan of running "vi" and expecting vim. Sounds a bit
like running "mozilla" and expecting "firefox" or... something.

-AT
-- 
Andrei Thorp, Developer: Xandros Corp. (http://www.xandros.com)

Freedom begins when you tell Mrs. Grundy to go fly a kite.


[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux