From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: possible bug in the way drafts works
Date: Thu, 02 Jan 2003 04:11:38 +0100 [thread overview]
Message-ID: <m3adikw8id.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <m3pu3svqlt.fsf@multivac.cwru.edu>
prj@po.cwru.edu (Paul Jarc) writes:
> Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
>> if you send a message, and then go back to that message buffer and
>> do some further editing. Then it'll be saved to the drafts group
>> again.
>
> In that case, could Gnus mark the draft article as 'sent or some such?
Hm, yes... After sending the message, I could add to the write-hook
thing a function that will save a header saying that it has already
been sent. Like
X-Message-Sent: yes
Or something like that. And then the message code could check that.
Would that cover all the cases? Hm...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2003-01-02 3:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 18:00 Harry Putnam
2002-01-26 22:44 ` Lars Magne Ingebrigtsen
2002-01-29 20:39 ` Paul Jarc
2003-01-02 3:11 ` Lars Magne Ingebrigtsen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3adikw8id.fsf@quimbies.gnus.org \
--to=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).