Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!uwm.edu!linac!att!cbfsb!cbnewsb.cb.att.com!mbb
From: mbb@cbnewsb.cb.att.com (martin.brilliant)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: Problem with Elvis 1.4
Message-ID: <1991Apr26.091618.16813@cbfsb.att.com>
Date: 26 Apr 91 09:16:18 GMT
References: <505@wrdis01.af.mil> <1991Apr25.182716.27779@cbfsb.att.com> <3248@mtecv2.mty.itesm.mx>
Sender: news@cbfsb.att.com
Distribution: na
Organization: AT&T Bell Laboratories
Lines: 21

In article <3248@mtecv2.mty.itesm.mx> josevela@mtecv2.mty.itesm.mx (Jose Angel Vela Avila) writes:
>>Elvis seems to want a directory called \TMP in your root directory.
>>If you have only one hard drive, that would be C:\TMP - I haven't
>>tried running Elvis in D: or E: yet.
>
> I tried it with c:\tmp from C: D: F: and don't works
>
> Are something wrong with Elvis ???

I just tried it in the D: drive, with a \TMP directory on drive C:,
and it works for me.  It also works on drive C:.  So there is some
very important difference between our setups that we don't know about
yet.  Does anybody have any clue to what's going on?

I think this is worth pursuing because I have found Elvis to be a
nearly perfect clone of the original vi.  The only thing it won't do
is send a block of text as input to the "shell" and replace the text
with the output, and that's because the DOS "shell" won't take
commands on standard input, so it's not a fault of Elvis.  Other
features work: key mapping, initialization file, reading the output of
a shell command, etc.