Bug "vi -r" ??

[David H. Brierley]

In article <43112 at sun.uucp> rdh at sun.UUCP (Robert Hartman) writes:
>In article <27000001 at ntvax> greg at ntvax.UUCP writes:
>> Does anyone know of a problem with the -r option of vi with 4.3BSD ?
>Well, you DO have to write the file before you quit.  Not doing so loses
>the recovered text.  This could probably be considered pilot error the
>second time it happens to a user.

What we did here was to modify vi so that when you use the -r flag it
automatically sets the flag indicating that the file has been changed.
The impact of this on the user is that if they try to quit without doing
a write they will get a message to that effect.  If you think about it
for a while this method makes a lot of sense since the file is only
preserved if you have made changes to it.
-- 
David H. Brierley
Raytheon Submarine Signal Division / 1847 West Main Road / Portsmouth, RI 02871

Phone:      (401)-847-8000 x4073
Internet:   dhb at rayssd.ray.com
Uucp:       {cbosgd, decuac, gatech, necntc, sun, uiucdcs, ukma} !rayssd!dhb