Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!rutgers!lll-lcc!ames!ucbcad!ucbvax!decvax!decwrl!pyramid!prls!mips!quacky!dce From: dce@quacky.UUCP (David Elliott) Newsgroups: comp.bugs.4bsd Subject: Re: Losing my work in vi! Message-ID: <120@quacky.UUCP> Date: Sat, 20-Dec-86 12:48:19 EST Article-I.D.: quacky.120 Posted: Sat Dec 20 12:48:19 1986 Date-Received: Sat, 20-Dec-86 22:38:48 EST References: <21107@styx.UUCP> <305@vsedev.VSE.COM> Reply-To: dce@quacky.UUCP (David Elliott) Organization: MIPS Computer Systems, Sunnyvale, CA Lines: 45 In article <305@vsedev.VSE.COM> ron@vsedev.UUCP (Ron Flax) writes: >In article <21107@styx.UUCP> carlson@styx.UUCP (John Carlson) writes: > >... > Guess what happens? That's right, all of my changes are lost! How > about setting the 'modified' flag whenever a restore is done? > >Which version of vi are you running? Mine which is 3.9, of 2/9/83 does >as you suggest. > There are two problems here: 1. The name of this newsgroup is comp.bugs.4bsd. 4.3BSD comes with ex version 3.7. If Ron is running a BSD system, how can he have 3.9, which is the version that comes with System V.3? Anyway, 4.3BSD is broken in this regard (unless someone walked on the sources again). 2. As pointed out recently in this newsgroup, the proper solution is to set the modified and not edited (really unsetting the edited) flags. If you just set the modified flag, this can happen: vi file ... system crash or phone line lost log in again continue editing save changes read mail and find out you need to recover, or just run vi -r vi -r file ZZ OOPS! You just undid your changes. By setting the 'not edited' state, you have to do a w!, which requires a little extra thought. At Tektronix, the people in Tony Birnseth's group changed vi to have a 'recovered' state. I don't know if this implied the above, but it was nice to do a :f or ^G and see '[Recovered]'. David Elliott Mips Computer Systems