Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!super.upenn.edu!eecae!upba!authorplaceholder
From: cory@upba.UUCP
Newsgroups: comp.bugs.4bsd
Subject: Re: vi BUG!!!!
Message-ID: <50100001@upba>
Date: Mon, 23-Nov-87 09:55:00 EST
Article-I.D.: upba.50100001
Posted: Mon Nov 23 09:55:00 1987
Date-Received: Thu, 26-Nov-87 03:21:27 EST
References: <11323@hc.DSPO.GOV>
Lines: 25
Nf-ID: #R:hc.DSPO.GOV:-1132300:upba:50100001:000:1172
Nf-From: upba.UUCP!cory    Nov 23 08:55:00 1987



	":w" is a feature of vi that writes the file.

	You can follow the write command with a file name to write to,
	or ">", ">>", or "|".  (Is that all or are there other allowed
	operators?)  When using the pipe sign, you are effectively using
	the shell, and it is out of vi's hands.  When using ">" or ">>"
	you are sending a current copy of the file being edited (we will
	call this file1) to or appended to the file named after the greater-
	than sign(s) (let's call this file2).  Vi really doesn't care what
	file2 is; if the file exists and you have write permission, Shazam;
	if the file does not exist and you have write permission in the
	directory, Shazam.

	Just because you choose to append to a file that you have write
	access to, but happen to be editing in read-only mode, makes no
	difference.  file1 and file2 are NOT related, and whether or not
	they are the same file doesn't matter.  It's not a bug.

					-Cory

...!ihnp4!upba!cory (Cory Dekker @ United Phone Book Advertisers)| DISCLAIMER:
Work: 1221 N St, Suite #800; Lincoln, NE 68508 {Ph: 402-476-2200}| You get what
Home: 800 Foxcroft Ct, #188; Lincoln, NE 68510 {Ph: 402-483-7761}| you pay for!