From: Lars Ingebrigtsen <larsi@gnus.org>
To: Nick Helm <nick@tenpoint.co.nz>
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 13:36:15 +0200 [thread overview]
Message-ID: <87r2nksllc.fsf@mouse.gnus.org> (raw)
In-Reply-To: <m2k1tdnxcl.fsf@tenpoint.co.nz> (Nick Helm's message of "Thu, 12 Apr 2018 11:21:14 +1200")
Nick Helm <nick@tenpoint.co.nz> writes:
>> 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.
Yeah, the Messsage buffers are kinda special, I guess, in that they're
basically the only Gnus buffers what aren't generated somehow.
So handling them the same way as Emacs does on shutdown does make some
sense... On the other hand, even if we prompt the user, they're still
saved to a pretty obscure place (i.e., the drafts group), so I'm not
sure we're gaining anything by prompting the user.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2018-04-12 11:36 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
2018-04-12 11:36 ` Lars Ingebrigtsen [this message]
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=87r2nksllc.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=28843@debbugs.gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=nick@tenpoint.co.nz \
/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.