On 2007-01-17 21:18:53 +0100, Romain Francoise wrote: > Backups are disabled in working copies because it's annoying to keep > backup versions when the same information is recorded in the version > control system...
As I explained, this is not the same information, because of intermediate (non-committed) contents. Anyway, there could be an option to remove the backups once the files have been committed. > The use case you describe of someone who does significant amounts of > work in a working copy but doesn't have write access is pretty > unusual in my experience, and in this case users can just set > `vc-make-backup-files' to t. In my experience, users don't always do a commit just after editing a file. And backups are precisely important when many changes have been done on a file. > I'd also like to note that relying on Emacs to backup important > information is unwise -- unless you set `version-control' to t, > you'll have only one backup and it gets overwritten every time you > visit the file: You missed the point. Emacs does that on *every* file. So, there is no surprise concerning this behavior. This is not the case with the behavior on version-control files; there is not a single warning from Emacs. > killing the buffer and reopening the file is enough to lose your > only backup. This is suboptimal. One shouldn't lose a backup until the buffer is modified and saved. And before modifying, one generally has the time to notice that the data are incorrect (e.g. after a "svn revert" in the wrong directory...). > P.S.: You might like to know that Emacs doesn't make backups of > files in or under /tmp, either. I noticed that in /var/tmp too. All these particular cases are annoying. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)
