Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!sdd.hp.com!ucsd!nosc!cod!jensen
From: jensen@cod.NOSC.MIL (Layne K. Jensen)
Newsgroups: comp.sys.atari.st
Subject: Elvis Problems
Keywords: elvis vi
Message-ID: <2339@cod.NOSC.MIL>
Date: 10 Oct 90 17:24:54 GMT
Distribution: na
Organization: Naval Ocean Systems Center, San Diego
Lines: 22

I picked up the Elvis binary that was recently distributed for the ST, and
am very impressed with the program.  As a vi addict, I can say that it is
certainly the closest to "real vi" of any implementations I have run across.

Now for the problem.  Elvis seems to leave residue in the system that causes
problems with other programs.  I first noticed that after using Elvis some
of my compiles (using the Sozobon compiler) would fail in strange ways, even
when the code hadn't been changed.  For example, after a reboot, a file
would compile and link with no problems, but as soon as I used Elvis (with
no changes to the source file), the compile would bomb, usually in the link
phase.  Also, my other version of "vi", Stevie, would no longer work.  It
would not "open the window", but would just wait until I stopped it with
a ":q<cr>" command, as if it was in open mode.

I have no idea what's going on, but it would make me feel better just to know
that someone else may have had similar experiences.

Thanks for listening,
-- 
Layne Jensen                           jensen@nosc.MIL
Naval Ocean Systems Center             ...!sdcsvax!noscvax!jensen
San Diego, CA