Gnus development mailing list
 help / color / mirror / Atom feed
From: jvinson@cheux.ecs.umass.edu (Jack Vinson)
Subject: Re: Killing *mail* and *postnews* buffers
Date: 30 Jan 1996 10:01:47 -0500	[thread overview]
Message-ID: <wospgxd8v8.fsf_-_@cheux.ecs.umass.edu> (raw)
In-Reply-To: <rjhgxdq5eq.fsf@ssv4.dina.kvl.dk>

>>>>> "PA" == Per Abrahamsen <abraham@dina.kvl.dk> writes:

PA> The drafts system is nice, but it has made it more difficult if you
PA> decide not to post/mail anyway.  I used just to kill the buffer with
PA> `C-x k RET'.  I suggest `C-c C-k' should remove the buffer from the
PA> draft directory, and kill it (after asking for confirmation).

I agree.  The old behavior of Gnus and mail was ask about the unfinished
message.  Now, if I do mail/post again, it just opens a new *Mail Gnus* buffer
and sticks the old message in the drafts group.

However, I just tried to edit an old draft that I could read in the Draft
group, but when I did 'S D c' to continue editing a draft it gave me an
error.  And when I just tried it again (to get a backtrace), the message
had disappeared from the Draft group.

I would also like to be warned that there are unfinished/undeleted drafts
sitting in the Draft group when I leave Gnus, in case I forgot to finish
writing a message.

-- 
Jack Vinson                       jvinson@cheux.ecs.umass.edu
"I Spit on Your Grave"            -- double feature at the drive-in as seen
"I Thumb Through Your Magazines"     from the Qwik-E mart


  parent reply	other threads:[~1996-01-30 15:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-01-30 11:38 Per Abrahamsen
1996-01-30 13:47 ` Kai Grossjohann
1996-01-30 16:38   ` Per Abrahamsen
1996-01-30 17:26   ` Steven L Baur
1996-01-30 18:20     ` Thomas Neumann
1996-01-30 15:01 ` Jack Vinson [this message]
1996-01-31 17:35 ` David L Jackson
1996-01-31 20:46 ` Lars Magne Ingebrigtsen
1996-01-31 20:56   ` Stainless Steel Rat
1996-01-31 21:05     ` Stainless Steel Rat

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=wospgxd8v8.fsf_-_@cheux.ecs.umass.edu \
    --to=jvinson@cheux.ecs.umass.edu \
    /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.
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 NNTP newsgroup(s).