Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!clyde!ho95e!wcs
From: wcs@ho95e.ATT.COM (Bill.Stewart)
Newsgroups: comp.cog-eng,comp.unix.xenix,comp.unix.wizards
Subject: Re: Request for human interface design anecdotes (and a cure?)
Message-ID: <1916@ho95e.ATT.COM>
Date: Sun, 6-Dec-87 17:35:32 EST
Article-I.D.: ho95e.1916
Posted: Sun Dec  6 17:35:32 1987
Date-Received: Fri, 11-Dec-87 20:47:02 EST
References: <3103@psuvax1.psu.edu> <1987Nov21.014754.19660@sq.uucp> <1987Nov27.011955.10801@sq.uucp> <771@hubcap.UUCP>
Reply-To: wcs@ho95e.UUCP (46133-Bill.Stewart,2G218,x0705,)
Organization: AT&T Bell Labs 46133, Holmdel, NJ
Lines: 19
Xref: mnetor comp.cog-eng:356 comp.unix.xenix:1285 comp.unix.wizards:5884

In article <771@hubcap.UUCP> hubcap@hubcap.UUCP (Mike Marshall) writes:
:I agree. I can be as scatter brained as they come, but I have cultivated the
:above habit, and I don't think I have EVER lost any files with "rm * .o" 

Must be nice.  I had a spurious file once, called * , and removed it.
I realized what I'd done about the time the $ came back; this was when
I learned about nightly backups (the administrators did them), and rm -i.

At Purdue, the local version of 4.*BSD had modified rm to move things
to /tmp/graveyard instead of really deleting them; they'd stick around
48 hours or so.  You could use the real rm if you wanted to.  Of
course, this doesn't prevent other ways of trashing files, though
noclobber helps.  One of the few things I appreciate about VMS is the
file versioning; every time you modify a file, it creates a new copy of
it (I assume at open-file-for-writing time?).  Even a one-deep automatic
backup would be helpful; emacs does this but vi and ed don't.
-- 
#				Thanks;
# Bill Stewart, AT&T Bell Labs 2G218, Holmdel NJ 1-201-949-0705 ihnp4!ho95c!wcs