Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!samsung!munnari.oz.au!uhccux!lee
From: lee@uhccux.uhcc.Hawaii.Edu (Greg Lee)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: elvis problems and a warning
Message-ID: <10297@uhccux.uhcc.Hawaii.Edu>
Date: 16 Nov 90 00:01:19 GMT
References: <3743@stl.stc.co.uk>
Organization: University of Hawaii
Lines: 33

From article <3743@stl.stc.co.uk>, by ndh@stl.stc.co.uk (Neale D Hind ):
>In article <814@iss-rb.SanDiego.NCR.COM> davel@booboo.SanDiego.NCR.COM (David Lord) writes:
>>...
>>	"WARNING: Disk write attempted to system area. Continue, Disallow, ...?"
>>
>elvis, when called with a filename, creates a copy of the file in the
>in the defined 'temp' directory against which all editing is performed.

But it does this regardless of whether a file name was given on the command
line, I think.  Whereas Norton diskmon issues the warning only when a file
name was given on the command line, as Neale said.

It would be nice to know what is going on here.  I really like elvis -- it's
better than vi.

After verifying the problem, I tried replying 'Y' when the Norton security
program asked whether to allow the supposed disk write to the system area.
The screen was not normal when elvis displayed the first page of file text --
cursor update characters seem to be displayed instead of obeyed.  Later,
Norton's Disk Doctor reported no problems with the system area.

>...
>>   	'elvis' absolutely will not run with that in your environment. As
>>   	far as I can tell, the only thing it will allow TEMP to be set to
>>   	is '.'.

Here, elvis seems happy to use windows/temp for its temporary files when
TEMP is set as described.  In regard to the TERM variable, the elvis code
checks to see if it is either "ansi" or "nansi", but I don't see why it
should become confused if it is neither.  I have it set to "nansi", and
that works ok (and doesn't give that disgusting blue background).

				Greg, lee@uhccux.uhcc.hawaii.edu