GNU bug report logs - #21612
24.5; Configuration variable to delete auto-save file when intentionally killing buffer

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 21612 <at> debbugs.gnu.org, monnier <at> iro.umontreal.ca, rms <at> gnu.org, mrok4a <at> gmail.com
Subject: bug#21612: 24.5; Configuration variable to delete auto-save file when intentionally killing buffer
Date: Mon, 23 Aug 2021 21:57:29 +0300

> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Cc: monnier <at> iro.umontreal.ca,  mrok4a <at> gmail.com,  21612 <at> debbugs.gnu.org,
>   rms <at> gnu.org
> Date: Mon, 23 Aug 2021 18:40:40 +0200
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > Hmm... bother.  If the new variable kill-buffer-delete-auto-save-files
> > is non-nil, we ask the user even if we eventually don't delete the
> > auto-save file, for example if auto-save-visited-mode is in effect.
> > Is that TRT?
> 
> If that's the case, it's a bug.  I'll have a look at this tomorrow.

Actually, if auto-save-visited-mode is on, the buffer will not be
modified after auto-saving.  But the general concern is still there:
we ask the question before we decide whether to delete, which I think
could cause trouble some day.

> > Also, I'd bet people would like to be able to delete them without any
> > questions asked, so maybe the variable should be a tristate, not a
> > boolean?
> 
> I think that's too dangerous, really, so I'd rather not.  But if others
> feel strongly that that should be a feature, I wouldn't oppose it.

Fair enough.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.