From: Nick Helm <nick@tenpoint.co.nz>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>, 28843@debbugs.gnu.org
Subject: bug#28843: 26.0.90; gnus kills unsaved message buffer
Date: Thu, 12 Apr 2018 11:21:14 +1200 [thread overview]
Message-ID: <m2k1tdnxcl.fsf@tenpoint.co.nz> (raw)
In-Reply-To: <87po35xwcn.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Wed, 11 Apr 2018 23:32:40 +0200")
On Thu, 12 Apr 2018 at 09:32:40 +1200, Lars Ingebrigtsen wrote:
> Nick Helm <nick@tenpoint.co.nz> writes:
>
>> One way to do that might be to kill unsaved message buffers earlier in
>> the gnus exit process, say with `gnus-exit-gnus-hook', and rely on
>> Emacs's standard unsaved buffer query to do `save-buffer' or
>> `message-dont-send'. Gnus is still running at that point, so it should
>> save to the drafts group just fine.
>
> But haven't the buffers already been saved earlier in the shutdown by a
> `do-auto-save'? That how I interpret Katsumi in bug#26862...
Yes they have, but I was suggesting to remove that auto-save mechanism
and find a way to prompt the user to save the draft instead, mimicking
what happens when Emacs is shut down with an unsaved buffer.
next prev parent reply other threads:[~2018-04-11 23:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-15 7:46 bug#28843: 26.0.90; gnus kills unsaved message buffer Nick Helm
2017-10-26 0:52 ` Nick Helm
2017-11-08 2:28 ` Nick Helm
2017-11-08 2:41 ` Eric Abrahamsen
2017-11-08 3:49 ` Nick Helm
2017-11-08 16:22 ` Eric Abrahamsen
2018-04-11 21:32 ` Lars Ingebrigtsen
2018-04-11 23:21 ` Nick Helm [this message]
2018-04-12 11:36 ` Lars Ingebrigtsen
2018-04-14 3:11 ` Nick Helm
2018-04-14 13:01 ` Lars Ingebrigtsen
2018-04-14 20:16 ` Nick Helm
2018-04-15 13:49 ` 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=m2k1tdnxcl.fsf@tenpoint.co.nz \
--to=nick@tenpoint.co.nz \
--cc=28843@debbugs.gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=larsi@gnus.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.