Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!nrl-cmf!ames!hc!siegel
From: siegel@hc.DSPO.GOV (Josh Siegel)
Newsgroups: comp.bugs.4bsd
Subject: Re: vi BUG!!!!
Message-ID: <11438@hc.DSPO.GOV>
Date: Fri, 20-Nov-87 15:08:49 EST
Article-I.D.: hc.11438
Posted: Fri Nov 20 15:08:49 1987
Date-Received: Sun, 22-Nov-87 15:13:10 EST
References: <11323@hc.DSPO.GOV> <16660001@hpisod2.HP.COM>
Reply-To: siegel@hc.dspo.gov.UUCP (Josh Siegel)
Organization: Group E-10, Los Alamos National Laboratory, NM
Lines: 34

In article <16660001@hpisod2.HP.COM> decot@hpisod2.HP.COM (Dave Decot) writes:
 >> Try the following:
 >> 	% cp .login goo
 >> 	% view goo
 >> 	{inside vi}
 >> 	:w>> goo
 >> 
 >> you have just appended to a file you opened Read Only....
 >> 
 >> BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG BUG
 >> 
 >
 >Not only that!  You can also do:
 >
 >   :!/bin/rm -f goo
 >
 >and the file will be GONE!  OH NO!
 >
 >If you don't get the sarcasm, this is a feature.

I think vi should check to see if you are appending to the
current file.  If I do a 

	view o.c
	:w>>

and hit return,  I specificly specified to append to the current file.
Problem was that it was read only. Why don't you get your head out
of the sand and look at what he posted.

			--Josh Siegel
-- 
Josh Siegel		(siegel@hc.dspo.gov)
  Friends don't let Friends eat Cherry Zingers