Path: utzoo!yunexus!ists!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!swrinde!gem.mps.ohio-state.edu!uwm.edu!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!auriga!altair!boyle
From: boyle@altair.mcs.anl.gov
Newsgroups: comp.sys.next
Subject: Re: Suspending vi
Message-ID: <4000004@altair>
Date: 18 Nov 89 17:38:41 GMT
Article-I.D.: altair.4000004
References: <3574@hydra.gatech.EDU>
Lines: 20
Nf-ID: #R:hydra.gatech.EDU:3574:altair:4000004:000:826
Nf-From: altair.mcs.anl.gov!boyle    Nov 17 22:22:00 1989


/* Written 12:22 pm  Nov 17, 1989 by gil@daffy.gatech.edu in altair:comp.sys.next */
/* ---------- "Suspending vi" ---------- */
I am running NeXT 1.0 and it seems to me that when I suspend vi
(via csh's ^Z, for example), vi insists upon first saving the
file being edited (if it has been changed).  [...] This
problem is especially troublesome if you happen to be editing
a file that you own but which you cannot write.  You cannot
suspend the editor, go to the shell, change the mode of the
file, resume and save. [...] 

				- Gil Neiger
				gil@daffy.gatech.edu
/* End of text from altair:comp.sys.next */

Presumably, besides doing ":set noautowrite", you could use ":w <file name>"
to write to some other file.  Or, you could use ":shell" to get a shell
within vi from which you could change the permissions.

Jim Boyle