Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!nmtsun!caasnsr
From: caasnsr@nmtsun.nmt.edu (Clifford Adams)
Newsgroups: comp.misc
Subject: Re: UNIX needs a real text editor
Message-ID: <2300@nmtsun.nmt.edu>
Date: 18 Mar 89 08:14:37 GMT
References: <222@imspw6.UUCP> <9653@bloom-beacon.MIT.EDU> <5552@brspyr1.BRS.Com> <1057@ncrcce.StPaul.NCR.COM>
Reply-To: caasnsr@nmtsun.nmt.edu (Clifford Adams)
Organization: New Mexico Tech, Socorro NM
Lines: 32

In article <5552@brspyr1.BRS.Com> miket@brspyr1.BRS.Com (Mike Trout)
writes:
>: You can use vi all you want, and it may work just fine for
you.  Fine; that's your business.  But you should be aware that
while you are putt-putting along in your Sopwith Pup, most of the
rest of us have climbed into P-38 Lightnings.  You may be very
comfortable with the Pup, but the real world has left you behind.

	First of all, I'm a spoiled GNUmacs user.  I like a lot of the
features of the editor.

	But I have my limits.

	I have recently been working with a HP9000 series 300.  Not
the fastest machine around.  Emacs (Unipress) takes over 60 seconds to
load on that machine.  I finally got fed up with it and learned the
basics of VI.  VI takes less than 5 seconds to load on that machine.
I got the basics of VI in about 10 minutes, and was reasonably
comfortable typing C code in about an hour.  I still use Emacs for
large/long typing jobs, but for short tasks, or debugging, VI is my
choice.

	I know--I should work with a faster machine.  For some reason
they won't let me use the Cray for Emacs, however :-).

[I'm testing the distribution of this message.  If you are in the Mid
or Southwestern US and see this message, please mail me a note.
Thanks.]
-- 
 Clifford A. Adams    ---    "I understand only inasmuch as I become."
 caasnsr@nmt.edu            ...cmcl2!lanl!unm-la!unmvax!nmtsun!caasnsr
 (505) 835-6104 | US Mail: Box 2439 Campus Station / Socorro, NM 87801