From: Dan Christensen <jdc@uwo.ca>
Subject: Re: spurious articles appearing in draft group
Date: Thu, 16 Sep 2004 23:10:58 -0400 [thread overview]
Message-ID: <877jqttwsd.fsf@uwo.ca> (raw)
In-Reply-To: <m3656dkhl6.fsf@pigpen.waxrat.com> (Michael Cook's message of "Thu, 16 Sep 2004 17:51:49 -0400")
Michael Cook <michael@waxrat.com> writes:
> okay, it seems i can reproduce this problem by editing an article
> (gnus-summary-edit-article). the article then becomes a
> rogue/zombie thing that keeps re-appearing in my drafts folder until
> i restart gnus.
For the record, I get the problem even when I'm not editing articles.
Dan
next prev parent reply other threads:[~2004-09-17 3:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 20:03 Dan Christensen
2004-09-15 20:21 ` Derrell.Lipman
2004-09-16 7:26 ` Christoph Conrad
2004-09-15 20:26 ` Michael Cook
2004-09-16 21:51 ` Michael Cook
2004-09-17 3:10 ` Dan Christensen [this message]
2004-09-29 7:48 ` Arnaud Giersch
2004-09-29 15:26 ` Arnaud Giersch
2004-10-01 6:21 ` Katsumi Yamaoka
2004-10-01 12:20 ` Stefan
2004-10-30 8:58 ` Arnaud Giersch
2004-11-04 6:30 ` Katsumi Yamaoka
2004-11-04 6:33 ` Christoph Conrad
2004-11-04 14:47 ` Ian Soboroff
2004-11-05 15:05 ` Ian Soboroff
2004-11-05 17:07 ` Arnaud Giersch
2004-11-07 23:59 ` Katsumi Yamaoka
2004-09-15 20:50 ` Christoph Conrad
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=877jqttwsd.fsf@uwo.ca \
--to=jdc@uwo.ca \
/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).