Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!rutgers!mit-eddie!greg From: greg@nosc.arpa@vis.UUCP Newsgroups: comp.emacs Subject: concerning Gnu Emacs backup files Message-ID: <8701092038.AA08699@vis.COM> Date: Fri, 9-Jan-87 15:38:42 EST Article-I.D.: vis.8701092038.AA08699 Posted: Fri Jan 9 15:38:42 1987 Date-Received: Sat, 10-Jan-87 01:54:16 EST Sender: daemon@mit-eddie.MIT.EDU Lines: 32 Date: Sun, 4 Jan 87 22:07:48 EST From: nosc!rms@prep.ai.mit.edu (Richard M. Stallman) To: info-gnu-emacs@prep.ai.mit.edu In-Reply-To: John Foderaro's message of Sun, 04 Jan 87 11:28:08 PST Subject: concerning Gnu Emacs backup files The purpose of backup files is to stay around for a while so you can back out of mistakes. Backup files are not out of date until months have gone by and it is no longer likely you will come across a bug. How can this be? If I make major changes to a file, then go back and put in a missing semicolon, the interesting backup is lost. Only a backup system with version numbers or an RCS-like change file can really give you the kind of capability you describe. Unfortunately, numbered backups use too much storage and running RCS takes too much time. I'm not familiar with the code for undoing, but would it be difficult to write (or append) the changes to a file, as an alternative to the current arrangement of keeping the changes in memory and a single backup file on disk? _Greg J. Greg Davidson Virtual Infinity Systems +1 (619) 452-8059 6231 Branting St; San Diego, CA 92122 USA greg@vis.uucp ucbvax--| telesoft--| vis!greg@nosc.arpa decvax--+--sdcsvax--+--vis vis!greg@sdcsvax.ucsd.edu ihnp4--| noscvax--|