Xref: utzoo comp.sys.ibm.pc:29309 comp.binaries.ibm.pc.d:3180
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!njin!princeton!phoenix!jwbirdsa
From: jwbirdsa@phoenix.Princeton.EDU (James Webster Birdsall)
Newsgroups: comp.sys.ibm.pc,comp.binaries.ibm.pc.d
Subject: Re: vi editor
Message-ID: <8681@phoenix.Princeton.EDU>
Date: 25 May 89 17:12:26 GMT
References: <24788@beta.lanl.gov> <554@megatek.UUCP>
Reply-To: jwbirdsa@phoenix.Princeton.EDU (James Webster Birdsall)
Followup-To: comp.sys.ibm.pc
Distribution: usa
Organization: Princeton University, NJ
Lines: 29

In article <554@megatek.UUCP> hollen@eta.megatek.uucp (Dion Hollenbeck) writes:
>From article <24788@beta.lanl.gov>, by pt@beta.lanl.gov (Paul A. Thiessen):
>> I know it has been mentioned before, but can someone please tell me where to
>> get a good VI editor for the PC?
>        ^^^^
>Good editor and VI in the same breath are oxymoronic.  Why not take the
>time to learn a REAL editor on which is made for the PC?  They are so
>much better than VI, that you will be surprised how you lived with
>VI for so long.  VI was hot shit when yoiu could only guarantee a
>serial terminal with alphabet and control keys, [stuff deleted]
>	Dion Hollenbeck             (619) 455-5590 x2814
>	Megatek Corporation, 9645 Scranton Road, San Diego, CA  92121

   There are other considerations. I have a REAL editor. The bloody
thing takes about 45 seconds to load (from a hard drive) and get itself
initialized. If I want to change one word in a small file, it takes much
longer to pull up the editor than it does to make the change. Whereas VI
loads in about five seconds and provides enough functionality to make
small changes like so.

   Save REAL editors for REAL uses, like writing papers. As a
quick-and-dirty editor for small changes, VI still has a place on my
drive.


-- 
James W. Birdsall  jwbirdsa@phoenix.Princeton.EDU  jwbirdsa@pucc.BITNET
   ...allegra!princeton!phoenix!jwbirdsa   Compu$erve: 71261,1731
"For it is the doom of men that they forget." -- Merlin