unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>, 26862@debbugs.gnu.org
Subject: bug#26862: Quit Gnus prompts about unsent messages, but messages can't be saved as drafts
Date: Thu, 11 May 2017 15:01:29 +0900	[thread overview]
Message-ID: <b4mvap8yls6.fsf@jpl.org> (raw)
In-Reply-To: <8737cdpdjj.fsf@ericabrahamsen.net>

On Wed, 10 May 2017 11:27:05 +0200, Stephen Berman wrote:
> However, when I restart Gnus, I see that that unsent message is in the
> Drafts group, i.e., Gnus in fact saved it.  So it's a UI bug but doesn't
> lose data.

Good point.  Yes, nndraft runs the auto-save on a modified draft
with a certain period.  Prompting a user for a modified draft is
a normal operation of `kill-buffer', not Gnus' intention.  So we
may kill those buffers safely and silently.

On Wed, 10 May 2017 18:42:33 +0900, Katsumi Yamaoka wrote:
> It seems hard to make `C-c C-d' work in such a case.  Instead,
> how about killing those modified message buffers unconditionally?

Thanks Eric for suggestions and verifying a revised patch.  I've
committed it in master:
<http://lists.gnu.org/archive/html/emacs-diffs/2017-05/msg00237.html>

Where `do-auto-save' makes sure that latest drafts are saved.
(set-buffer-modified-p nil) is necessary to kill modified buffers
silently.
(setq kill-buffer-hook nil) assumes that a user might set it for
a certain purpose (I do it ;-), that might issue a useless prompt.

Regards,





      reply	other threads:[~2017-05-11  6:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10  3:59 bug#26862: Quit Gnus prompts about unsent messages, but messages can't be saved as drafts Eric Abrahamsen
2017-05-10  9:27 ` Stephen Berman
2017-05-10  9:42 ` Katsumi Yamaoka
2017-05-11  6:01   ` Katsumi Yamaoka [this message]

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b4mvap8yls6.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=26862@debbugs.gnu.org \
    --cc=eric@ericabrahamsen.net \
    --cc=stephen.berman@gmx.net \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).