Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!ames!pasteur!ucbvax!hplabs!hpl-opus!hpnmdla!suew
From: suew@hpnmdla.HP.COM (Sue Wood)
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Re: stevie editor
Message-ID: <9280001@hpnmdla.HP.COM>
Date: 6 Mar 90 21:25:28 GMT
References: <2PSFZ5W@drivax.UUCP>
Organization: HP Network Measurements Div, Santa Rosa, CA
Lines: 32

/ hpnmdla:comp.sys.ibm.pc.programmer / braun@drivax.UUCP (Kral) / 11:08 am  Mar  5, 1990 /


I too am a vi fan.  I used to have the mks toolkit running on my pc
but since I bought my 386 I haven't used it.  (I'm checking out another
shell).  However, I miss vi too much so I wanted to run it on top of this
other shell (4DOS by the way).  It will run by it gives me file errors.
Can't remember the exact error message.  Is this what you're referin
to in the next line:

>I'm using ver 2.3d of the toolkit.  Vi (and other programs) seem to want the
>toolkit's shell under them.  My only *real* complaints are
  ^^^^^^^^^^^^^^^^^^^^^^^^

>
>1.	You have to be in the directory of the file you want to edit (eg,
>	if you are in c:\subdir, and you type 'vi \autoexec.bat', you get
>	some sort of error (I don't recall what it is  right now).

I don't recall having this problem!!  I'c categorize this as a major
annoyance.

>
>3.	It's in black and white.  While this isn't a real show stopper,
>	it's rather hard on the eyes that have been staring at a color
>	screen for a while.
>

Here's another question.  I'd like to integrate vi into the MS QuickC
environment.  Do you know if this is possible?  Ever tried it?

Sue