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: Sun, 15 Apr 2018 08:16:15 +1200 [thread overview]
Message-ID: <m2vactsfw0.fsf@tenpoint.co.nz> (raw)
In-Reply-To: <87tvsej62a.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Sat, 14 Apr 2018 15:01:01 +0200")
On Sun, 15 Apr 2018 at 01:01:01 +1200, Lars Ingebrigtsen wrote:
> Nick Helm <nick@tenpoint.co.nz> writes:
>
>> Personally, I think prompting gains us quite a bit. Most importantly, it
>> can remind users that an un-dealt-with message exists. Maybe they
>> intended to send it, but forgot, or mis-keyed? Or perhaps it contains
>> sensitive info that shouldn't be kept? By silently saving (to a
>> pretty obscure place) the user may never know about it.
>
> Yeah, that's true. You've convinced me. :-)
That's great, thanks!
> Do you have a patch to make Gnus prompt at the right time (while it's
> still early enough that messages can be sent etc)?
I'm afraid I only got as far as thinking about how it might work,
possibly using `gnus-exit-gnus-hook', but that's about it.
next prev parent reply other threads:[~2018-04-14 20:16 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
2018-04-14 3:11 ` Nick Helm
2018-04-14 13:01 ` Lars Ingebrigtsen
2018-04-14 20:16 ` Nick Helm [this message]
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=m2vactsfw0.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.