From: Josh <huber+news@alum.wpi.edu>
Subject: Re: Drafts group not replacing old messages
Date: Fri, 19 Nov 2004 13:32:13 -0500 [thread overview]
Message-ID: <87wtwh3d1u.fsf@huber.callisto.paradoxical.net> (raw)
In-Reply-To: <87brdw9rbo.fsf@mid.packer.its.vanderbilt.edu>
"Andrew A. Raines" <aaraines@pobox.com> writes:
> [snip repro directions]
I just did this a couple times in the gnus.test group...
> So it seems like one iteration of compose, draft, re-edit, send
> works properly, but if there's another `D e' thrown in, it
> breaks. That's my observation; I could be missing something
> obvious. However, I don't see why someone would want the old
> drafts accumulating like that. It's too easy to hit `J S' and
> spam the recipient.
This seems to work for me...
I'm using "No Gnus v0.3", with Emacs 21.3.50.1. (cvs build)
Josh
next prev parent reply other threads:[~2004-11-19 18:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 21:55 Andrew A. Raines
2004-11-15 22:07 ` Andrew A. Raines
2004-11-17 19:20 ` Josh
2004-11-17 20:02 ` Andrew A. Raines
2004-11-19 18:32 ` Josh [this message]
2004-11-26 20:36 ` ECB breaks Gnus (was: Drafts group not replacing old messages) Andrew A. Raines
-- strict thread matches above, loose matches on Subject: below --
2004-11-15 21:42 Drafts group not replacing old messages Andrew A. Raines
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=87wtwh3d1u.fsf@huber.callisto.paradoxical.net \
--to=huber+news@alum.wpi.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).