tjr@cbnewsc.att.com (thomas.j.roberts) (08/29/90)
I got elvis to compile, link, and (aparently) run correctly on a PC,
using Turbo C 2.0. What I did:
1) use the integrated environment (tc), in LARGE model, using the
supplied elvis.prj. Make sure your INCLUDE and LIBRARY directories
are set properly, etc.
2) in elvis.prj, delete all of the "termcap/*" lines at the end, and add
"tinytcap".
3) Hit <F9> (make), and you get a gazillion warnings ("code has no effect",
"questionable assignment") - they all seem OK, so I ignored them.
It compiles and links with no errors. When run "elvis *.h", get the
message "Bad command", but it then works OK; no such message if
* and ? are NOT used in the argument list. As supplied, elvis
executes "wildcard" to expand the arguments, and it could not
find it (because I had not built it). Building "wildcard" in
the current directory went OK, but elvis still could not find it.
I edited "main.c" to treat MSDOS just like UNIX, because I have
added Turbo C's WILDARG.OBJ to CL.LIB, so that arguments are already
expanded before main() is called. After re-making elvis, it now seems
to work OK (no messages, * and ? expanded properly).
I have NOT given it an exhaustive test, but it has performed every
command I have given it, and has not bombed anything. The execuable
file elvis.exe is 160 kilobytes long. On a 386/SX, it took only a few
minutes to build; the screen appears to be roughly equivalent to
19200 baud. It uses environment variables TMP or TEMP to place its
temporary files, so they go to my RAMDISK; file I/O seems not to
be a bottleneck.
Much Thanks to Steve Kirkendall for posting this VERY useful
program, and for EXCELLENT style. Thanks also for posting source,
as we are prohibited from using binaries from USENET (viruses,
you know).
Tom Roberts
att!ihlpl!tjrob