Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!dog.ee.lbl.gov!elf.ee.lbl.gov!torek
From: torek@elf.ee.lbl.gov (Chris Torek)
Newsgroups: comp.editors
Subject: Re: :wq (Re: One user's editor wish list)
Message-ID: <11638@dog.ee.lbl.gov>
Date: 30 Mar 91 18:35:53 GMT
References: <1991Feb22.134323.20410@scrumpy@.bnr.ca> <1991Mar25.191821.11019@scrumpy@.bnr.ca> <2900@wn1.sci.kun.nl> <1991Mar29.160622.5445@informix.com>
Reply-To: torek@elf.ee.lbl.gov (Chris Torek)
Organization: Lawrence Berkeley Laboratory, Berkeley
Lines: 17
X-Local-Date: Sat, 30 Mar 91 10:35:53 PST

In article <1991Mar29.160622.5445@informix.com> dberg@informix.com
(David I. Berg) writes:
>... Once upon a time a system crashed during a long and arduous edit
>session. When the system came back up, I successfully recovered my
>file with vi -r, but had other things to do just then, so I
>autumatically entered ZZ and went on with my business.

This is a bad idea, and not only because in some version of vi it does
not write the file anywhere.  You should *always* write recovered files
to a new (temporary) name and compare the original and new files
manually, as it is possible for recovered files to be partially
mangled.  In most cases, the recovered file will be correct, but in a
few cases you can get back almost all of your work only by merging the
original and new files.
-- 
In-Real-Life: Chris Torek, Lawrence Berkeley Lab CSE/EE (+1 415 486 5427)
Berkeley, CA		Domain:	torek@ee.lbl.gov