This is Suspending-vi in view mode; [Up]
Date: Sun 17-Nov-1989 18:22:15 From: Unknown Subject: 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). I don't remember this from 0.8 or other versions of vi that I have used. 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. Vi does not let you suspend because you cannot write the file! - Gil Neiger gil@daffy.gatech.edu >From: ali@polya.Stanford.EDU (Ali T. Ozer)
Date: Sun 17-Nov-1989 22:08:42 From: Unknown Subject: Re: Suspending vi In article <3574@hydra.gatech.EDU> gil@daffy.gatech.edu (Gil Neiger) writes: >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). vi on my machine doesn't do that; do you have some option set, maybe? (I'm not familiar with vi so I don't know what would cause this; however, it doesn't seem to be the default behavior.) Ali >From: sahayman@iuvax.cs.indiana.edu (Steve Hayman)
Date: Sun 17-Nov-1989 23:09:07 From: Unknown Subject: Re: Suspending vi >(I'm not familiar with vi so I don't know what would cause this; >however, it doesn't seem to be the default behavior.) This behaviour of vi [automatically writing out files when you ^Z] is called "autowrite", and is set with ":set autowrite" or ":set aw". It shouldn't be anybody's default; check your EXINIT variable or .exrc file. You can turn it off with ":set noaw", which is handy if you're trying to suspend a vi session and the file can't be written. >From: surak@jessica.Stanford.EDU (Jayson Adams)
Date: Sun 18-Nov-1989 17:38:41 From: Unknown Subject: Re: Suspending vi /* 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 >From: bchen@eeyore.caltech.edu (Bing-Qing Chen)
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Marcel Waldvogel and Netfuture.ch.