From: Lars Ingebrigtsen <larsi@gnus.org>
To: Marcus <mrok4a@gmail.com>
Cc: 21612@debbugs.gnu.org
Subject: bug#21612: 24.5; Configuration variable to delete auto-save file when intentionally killing buffer
Date: Mon, 16 Aug 2021 14:36:40 +0200 [thread overview]
Message-ID: <87im05d0rr.fsf@gnus.org> (raw)
In-Reply-To: <CAGOzRoxKP7RMpJCo=Nr3p4mkT5Jg-wY8_vjJEmz=uGqVcuyA-g@mail.gmail.com> (Marcus's message of "Sat, 3 Oct 2015 16:51:12 +0200")
Marcus <mrok4a@gmail.com> writes:
> Recipe for recreating:
> Start Emacs: `emacs -Q'
> Visit a file, e.g.: `C-x C-f RET test-file RET'.
> Change the file, e.g.: `M-> Will this auto-save?'
> Trigger auto-save, e.g. by idling for 30 seconds
> Quit Emacs: `C-x C-c RET'
> Don't save the file: `n yes RET'
> Start Emacs again: `emacs -Q'
> Visit the same file, e.g.: `C-x C-f RET test-file RET'
> Message "test-file has auto save data; consider M-x recover-this-file"
> appears.
>
> Since the buffer was killed intentionally, shouldn't it be possible to
> configure Emacs such that the auto save file will be deleted?
I think that sounds like a reasonable feature -- I can see people
getting annoyed at Emacs' behaviour here. Perhaps the way to implement
this would be to:
Quit Emacs: `C-x C-c RET'
Save file: `n'
Delete auto-save file?: `yes RET'
That is, introduce a new option that would offer to delete auto-save
files for buffers the user chooses not to save. This could even be done
generally -- not just during shutdown -- afer the
Buffer foo modified; kill anyway? yes RET
dialogue. (This would be an opt-in user option, of course, because the
current behaviour is safer.)
Any opinions?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-08-16 12:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-03 14:51 bug#21612: 24.5; Configuration variable to delete auto-save file when intentionally killing buffer Marcus
2015-10-03 17:03 ` Eli Zaretskii
2015-10-03 17:53 ` Marcus
2015-10-03 18:00 ` Eli Zaretskii
2021-08-16 12:36 ` Lars Ingebrigtsen [this message]
2021-08-16 13:06 ` Eli Zaretskii
2021-08-16 13:52 ` Lars Ingebrigtsen
2021-08-16 14:10 ` Eli Zaretskii
2021-08-16 18:48 ` Lars Ingebrigtsen
2021-08-18 12:45 ` Lars Ingebrigtsen
2021-08-18 13:34 ` Eli Zaretskii
2021-08-18 13:38 ` Lars Ingebrigtsen
2021-08-18 13:48 ` Eli Zaretskii
2021-08-18 14:31 ` Lars Ingebrigtsen
2021-08-18 16:13 ` Eli Zaretskii
2021-08-18 16:41 ` Lars Ingebrigtsen
2021-08-18 16:44 ` Eli Zaretskii
2021-08-19 13:05 ` Lars Ingebrigtsen
2021-08-20 6:23 ` Eli Zaretskii
2021-08-20 13:29 ` Lars Ingebrigtsen
2021-08-22 9:29 ` Eli Zaretskii
2021-08-22 21:55 ` Lars Ingebrigtsen
2021-08-23 12:21 ` Eli Zaretskii
2021-08-23 13:58 ` Lars Ingebrigtsen
2021-08-23 16:24 ` Eli Zaretskii
2021-08-23 16:40 ` Lars Ingebrigtsen
2021-08-23 18:57 ` Eli Zaretskii
2021-08-25 9:58 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87im05d0rr.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=21612@debbugs.gnu.org \
--cc=mrok4a@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).