From: Marcus <mrok4a@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21612@debbugs.gnu.org
Subject: bug#21612: 24.5; Configuration variable to delete auto-save file when intentionally killing buffer
Date: Sat, 3 Oct 2015 19:53:05 +0200 [thread overview]
Message-ID: <CAGOzRozBPPDT_ryJY-3hX11Rb79sQXB-_S2xA9jAe_-gfJ9qbQ@mail.gmail.com> (raw)
In-Reply-To: <83mvvz3mvk.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 865 bytes --]
> On Sat, Oct 3, 2015 at 7:03 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Sat, 3 Oct 2015 16:51:12 +0200
> > From: Marcus <mrok4a@gmail.com>
> >
> > This might even be useful default behavior.
> People sometimes answer YES by mistake.
Isn't that why the "Modified buffers exist" question is yes/no rather than
y/n?
> I guess it could be OK as an option for people who like to live
dangerously.
I do, and have so far implemented the functionality as (not with an option,
I don't know how):
(add-hook 'kill-buffer-hook 'delete-auto-save-file-if-necessary)
(add-hook 'kill-emacs-hook 'delete-auto-save-file-if-necessary)
If I figure out how to have this controlled by an option, where (and how)
would I send a patch request?
BTW, is my mailing list etiquette (formatting of replies etc.) acceptable?
This is my first bug report to a free software project.
[-- Attachment #2: Type: text/html, Size: 1552 bytes --]
next prev parent reply other threads:[~2015-10-03 17:53 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 [this message]
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
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=CAGOzRozBPPDT_ryJY-3hX11Rb79sQXB-_S2xA9jAe_-gfJ9qbQ@mail.gmail.com \
--to=mrok4a@gmail.com \
--cc=21612@debbugs.gnu.org \
--cc=eliz@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.