Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!rdh
From: rdh@sun.uucp (Robert Hartman)
Newsgroups: comp.bugs.4bsd
Subject: Re: Bug "vi -r" ??
Message-ID: <43280@sun.uucp>
Date: 26 Feb 88 07:35:47 GMT
References: <27000001@ntvax> <43112@sun.uucp> <1834@rayssd.ray.com>
Reply-To: rdh@sun.UUCP (Robert Hartman)
Organization: Sun Microsystems, Mountain View
Lines: 19

In article <1834@rayssd.ray.com> dhb@rayssd.RAY.COM (David H. Brierley) writes:
>In article <43112@sun.uucp> rdh@sun.UUCP (Robert Hartman) writes:
>>In article <27000001@ntvax> greg@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.  ...
>
>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.

I think that this arguably the right way to handle it.  It is consistent with
vi's behavior in all other cases where modifications have occurred.  -bob.

>-- 
>David H. Brierley
>Raytheon Submarine Signal Division / 1847 West Main Road / Portsmouth, RI 02871