Gnus development mailing list
 help / color / mirror / Atom feed
From: Dave Abrahams <dave@boostpro.com>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: ding@gnus.org
Subject: Re: How to forward / reply to my own post?
Date: Thu, 06 Oct 2011 17:46:43 -0400	[thread overview]
Message-ID: <m2lisxhjy4.fsf@pluto.luannocracy.com> (raw)
In-Reply-To: <m3ty7llt2l.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 06 Oct 2011 23:16:02 +0200")


on Thu Oct 06 2011, Lars Magne Ingebrigtsen <larsi-AT-gnus.org> wrote:

>> But, boy, what a pain.  I have to `C-c C-d', then go to my groups buffer,
>> refresh so drafts show up, pick the draft, and `F' to follow up.  

Oh, and then I have to delete the draft after sending.

>> It should be easier.
>
> Yes, I want this, too.  I especially wanted it back when the emacs-devel
> mailing list was so slow, and I wanted to follow up to something I'd
> just said, but then I had to wait forever, and forgot what I was going
> to say.
>
> So I think this should be implemented, but Emacs is in a feature freeze,
> so not now.

OK.  While we're mucking about in there, it would be nice if the buffer
name for messages in the drafts could be easily correlated with the
number under which they get saved, too :-)

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com



  reply	other threads:[~2011-10-06 21:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-23 11:50 Dave Abrahams
2011-07-23 18:04 ` Steinar Bang
2011-07-24  8:16   ` Peter Münster
2011-07-24 20:28     ` Steinar Bang
2011-09-29  9:22       ` Ted Zlatanov
2011-09-29 12:32         ` Dave Abrahams
2011-09-29 14:02           ` Ted Zlatanov
2011-10-06 21:16           ` Lars Magne Ingebrigtsen
2011-10-06 21:46             ` Dave Abrahams [this message]
2011-10-07  5:37               ` Sivaram Neelakantan
2011-07-24 17:10   ` Dave Abrahams
2011-07-24 20:33     ` Steinar Bang
2011-07-25 19:33       ` Dave Abrahams
2011-08-21  3:56 ` Lars Magne 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=m2lisxhjy4.fsf@pluto.luannocracy.com \
    --to=dave@boostpro.com \
    --cc=ding@gnus.org \
    --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.
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).