Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!nrl-cmf!ames!ucbcad!ucbvax!bostic
From: bostic@ucbvax.BERKELEY.EDU (Keith Bostic)
Newsgroups: comp.bugs.4bsd
Subject: Re: vi BUG!!!!
Message-ID: <21917@ucbvax.BERKELEY.EDU>
Date: Mon, 23-Nov-87 17:05:40 EST
Article-I.D.: ucbvax.21917
Posted: Mon Nov 23 17:05:40 1987
Date-Received: Thu, 26-Nov-87 07:22:29 EST
References: <11323@hc.DSPO.GOV> <4967@sdcrdcf.UUCP>
Organization: University of California at Berkeley
Lines: 15
Keywords: vi
Summary: you can circumvent this

In article <4967@sdcrdcf.UUCP>, pmontgom@sdcrdcf.UUCP (Peter Montgomery) writes:
> 	Relatedly, if goo is read only and you do
> 
> 		% vi goo
> 		(edits)
> 		ZZ
> 
> then it won't let you write there, even after you do a control-Z and a chmod.

Yes, but ":w! goo" will allow you to overwrite it.  The obvious problem
with vi checking the mode each time you attempt to write the file is the
semantics of someone else changing the mode of a file while you're editing
it.

--keith