From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21612@debbugs.gnu.org, mrok4a@gmail.com, rms@gnu.org
Subject: bug#21612: 24.5; Configuration variable to delete auto-save file when intentionally killing buffer
Date: Wed, 18 Aug 2021 18:41:36 +0200 [thread overview]
Message-ID: <87lf4yaenz.fsf@gnus.org> (raw)
In-Reply-To: <83h7fm4tpl.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 18 Aug 2021 19:13:10 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Actually, I'm not sure that my first reading of this code was correct.
>> Will this code ever trigger a file deletion?
>
> Why not?
Under which conditions will it delete anything? Hm... well, I guess if
you set the buffer to non-modified manually and then kills it, it'll
delete the auto-save file?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-08-18 16:41 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lf4yaenz.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=21612@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mrok4a@gmail.com \
--cc=rms@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.