From: Harry Putnam <reader@newsguy.com>
Subject: nndrafts squawk
Date: Sat, 09 Mar 2002 18:31:28 -0800 [thread overview]
Message-ID: <m17kolgnlr.fsf@reader.newsguy.com> (raw)
Its irritated me enough again to make me squawk some more.
The new behavior of nndrafts. By new I mean a couple mnths I think.
I keep finding things in drafts that I've already sent. It might be
an unfinished version or sometimes the whole thing. If I kill a
composition after its been setting a while, it ends up in drafts.
This is wrong wrong wrong, to my way of thinking, and definitely a big
change from the old behavior.
No one else seems bothered by it. The worst thing I see with this, is
finding a message a day or so later and then not being sure if it was
sent or not. Confusing and unecessary.
I want only C-c C-d to go to drafts and stay there. Absolutely
nothing else. No crashes no kills no baloney at all. Any thing
killed should vanish right then and there. I'd much prefer losing a
carefully created composition once a year than keep finding confusing
remnants or already sent stuff, or killed stuff in there.
Now how can I get that kind of behavior on my setup? Is there
something I can tweak, jiggle, twist or slap, to stop this behavior?
reply other threads:[~2002-03-10 2:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m17kolgnlr.fsf@reader.newsguy.com \
--to=reader@newsguy.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).