Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!mcsun!hp4nl!eutrc3!tuewsd!wsinkees From: wsinkees@lso.win.tue.nl (Kees Huizing) Newsgroups: comp.editors Subject: Re: vi abbreviation for :w :n ? Message-ID: <457@tuewsd.lso.win.tue.nl> Date: 12 Oct 89 11:56:32 GMT References: <4728@tekcrl.LABS.TEK.COM> <26465@iuvax.cs.indiana.edu> <5486@alvin.mcnc.org> <455@tuewsd.lso.win.tue.nl> <5574@alvin.mcnc.org> Organization: Eindhoven University of Technology, The Netherlands Lines: 31 ge@mcnc.org (George Entenman) writes: (talking about the dangers of the option 'autowrite' in vi) > And, I still can't help thinking that it might get you someday. > Let's see if I can imagine a scenario. Suppose that you have an > old vi job hanging around, forgotten. Suppose that you are busy > using '^Z' and 'fg' to get in and out of your file. Suppose you > quit that vi and don't notice the other vi in background. And > suppose that you absent mindedly type 'fg' to get back into vi. > If you don't notice that this is an old version of the file, you > are in danger of wiping out your work with another '^Z'. Tell > me if this ever happens to you! > ge@mcnc.org I must admit, this is a danger. I think that this happened to me when I had just learned about '^Z' and 'autowrite'. But I so seldom use 'ZZ' nowadays, that I don't fall into this trap anymore. My usual way to quit vi is now to type two times 'logout' :-) By the way, for those who love '^Z' and 'autowrite', here's a way to "suspend" vi even from input mode: map map! The ^X can be any key you don't use. It is needed to avoid "tail recursion". Kees -- Kees Huizing - Eindhoven Univ of Techn - Dept Math & Comp Sc - The Netherlands DOMAIN: wsinkees@win.tue.nl BITNET: wsdckeesh@heitue5 FAX: +31-40-436685