From: Derrell.Lipman@UnwiredUniverse.com
Subject: file improperly added to "drafts" by demon news/mail retrieval
Date: Thu, 29 Aug 2002 10:12:52 -0400 [thread overview]
Message-ID: <fzwx69ej.fsf@random.localnet.UnwiredUniverse.com> (raw)
I'm using Oort v0.06. I recently started having gnus retrieve my news/mail
automagically using:
(add-hook 'gnus-startup-hook
'(lambda ()
(gnus-demon-add-handler 'gnus-group-get-new-news 1 0)))
If I'm in the middle of writing a message when the daemon runs, it saves a
copy of the message that I'm writing in the "drafts" folder. (And it appears
to be an old copy, probably the most recent '#' file.) When I send the
message, this draft does not get deleted. To delete it, I must go into the
drafts folder and do B DEL. This differs from editing a draft with D E and
sending it; in that case, the draft gets deleted.
Is there a way to either tell the daemon not to save the draft that I'm
working on, or to have the draft properly deleted when I send the message?
Thanks!
Derrell
next reply other threads:[~2002-08-29 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-29 14:12 Derrell.Lipman [this message]
2002-12-29 19:51 ` 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=fzwx69ej.fsf@random.localnet.UnwiredUniverse.com \
--to=derrell.lipman@unwireduniverse.com \
/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).