fredch@guardian.hf.intel.com (01/23/91)
I have been thinking of using Steve Kirkendall's Elvis as an alternate to
the older PC/VI. I've hit upon a couple of quirks that seem to limit
its usefulness under DOS.
1) The documentation suggests that under DOS, elvis searches for
.\elvis.rc. In other words, only in your current directory. PC/VI,
on the other hand, will look in your HOME directory for vi.ini.
I don't care to have elvis.rc's sprinkled all other the place, so I
tried another tack (see below). Nevertheless, is there a way to get
elvis to search under HOME? (I do not have source, only the binary as
posted to c.b.i.p)
2) The documentation says that elvis will check with the EXINIT env var.
Unfortunately, command.com barfs on either of:
set EXINIT="ai re=1 sw=4"
set EXINIT=ai re=1 sw=4
Any solutions to this?
3) If I scroll with ^D, from end of text to end of screen line is black
instead of the normal background color. :g's do this, too, but not
^F's or j's, nor ^U's, ^B's, or k's. This is not fatal but annoying.
Thanks in advance. ...FredCh (fredch@starlite.hf.intel.com)
--
Fred Christiansen, Intel, JF1-67 503-696-4214 | fredch@starlite.hf.intel.com
5200 NE Elam Young Prkwy, Hillsboro, OR 97124 | uunet!intelhf!starlite!fredch
Children spell love this way: t-i-m-e. "Quality time" must be in quantity.mikef@bert.Rosemount.COM (Michael Foerster) (01/27/91)
In article <1991Jan22.185655.5047@intelhf.hf.intel.com> you write: >I have been thinking of using Steve Kirkendall's Elvis as an alternate to >the older PC/VI. I've hit upon a couple of quirks that seem to limit >its usefulness under DOS. > >1) The documentation suggests that under DOS, elvis searches for > .\elvis.rc. In other words, only in your current directory. PC/VI, > on the other hand, will look in your HOME directory for vi.ini. > I don't care to have elvis.rc's sprinkled all other the place, so I > tried another tack (see below). Nevertheless, is there a way to get > elvis to search under HOME? (I do not have source, only the binary as > posted to c.b.i.p) > What I did was to change the binary of the file by editing it with a PD binary file editor called "fm.com" (similar to the utility in the Norton Utilities) and changed every occurance of: elvis.rc to d:\vi.rc Note that the character count is the same. D: is the RAMDRIVE and on boot up I copy the "vi.rc" file to the d:\ directory. You can use the "c:\vi.rc" as well. Now when you invoke "elvis" it will look in the "D:\" for the "vi.rc" file and start up with the functions set in it. Only one file is then needed, not one in each directory. Mikef In article <1991Jan22.185655.5047@intelhf.hf.intel.com> you write: >I have been thinking of using Steve Kirkendall's Elvis as an alternate to >the older PC/VI. I've hit upon a couple of quirks that seem to limit >its usefulness under DOS. > >1) The documentation suggests that under DOS, elvis searches for > .\elvis.rc. In other words, only in your current directory. PC/VI, > on the other hand, will look in your HOME directory for vi.ini. > I don't care to have elvis.rc's sprinkled all other the place, so I > tried another tack (see below). Nevertheless, is there a way to get > elvis to search under HOME? (I do not have source, only the binary as > posted to c.b.i.p) > What I did was to change the binary of the file by editing it with a PD binary file editor called "fm.com" (similar to the utility in the Norton Utilities) and changed every occurance of: elvis.rc to d:\vi.rc Note that the character count is the same. D: is the RAMDRIVE and on boot up I copy the "vi.rc" file to the d:\ directory. You can use the "c:\vi.rc" as well. Now when you invoke "elvis" it will look in the "D:\" for the "vi.rc" file and start up with the functions set in it. Only one file is then needed, not one in each directory. Mikef