* Make nndrafts quit being overly helpful
@ 2002-02-09 6:05 Harry Putnam
2002-02-09 22:32 ` Paul Jarc
0 siblings, 1 reply; 2+ messages in thread
From: Harry Putnam @ 2002-02-09 6:05 UTC (permalink / raw)
A couple of months or so ago there were some changes made to nndrafts
that causes a behavior that is irritating, but more over I think it is
wrong behavior as well.
For several years now I've been using a technique to edit and save
messages or several messages by using either `e' or in the case of a
thread I might use S O m (gnus-uu-digest-mail-forward) to first create
a sort of digest. Then edit the whole thing.
I have a home made function I then invoke that sends the edited
message where ever I want it on my groups. I then kill the edit
buffer. My function is hooked into all edit modes so I can invoke
it in any composition or edit buffer.
For some time now, if the editing lasts long enough for auto save to
happen then the killed buffer (`S O m' `F' `R' but not `e') reappears
in nndrafts.
This can also happen if you start a composition then decide to trash
it. It might show up in nndrafts causing confusion as to what the game
plan was.
A purposely killed buffer should *NOT* reappear in nndrafts. No
killed or otherwise crashed, demised, curtailed or eschewed buffer
should.
Only drafts from either C-x C-s or preferable C-x C-d should go
there. Nothing else. After all it is a `drafts' group. Not a
recovery, crash, recycle, second chance, data recovery group.
Or AA clinic. :-)
Maybe it is difficult to tell the difference between a willfully
killed and crashed buffer, but in fact neither should be going to
drafts.
Do we need an nnrecover or nnMSrecyle_bin...? Seriously, that may be
a good thing to have. But it should not be drafts.
Can I do something locally to control this? I mean, short of major
coding.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Make nndrafts quit being overly helpful
2002-02-09 6:05 Make nndrafts quit being overly helpful Harry Putnam
@ 2002-02-09 22:32 ` Paul Jarc
0 siblings, 0 replies; 2+ messages in thread
From: Paul Jarc @ 2002-02-09 22:32 UTC (permalink / raw)
Harry Putnam <reader@newsguy.com> wrote:
> I have a home made function I then invoke that sends the edited
> message where ever I want it on my groups. I then kill the edit
> buffer. My function is hooked into all edit modes so I can invoke
> it in any composition or edit buffer.
>
> For some time now, if the editing lasts long enough for auto save to
> happen then the killed buffer (`S O m' `F' `R' but not `e') reappears
> in nndrafts.
You could send the message with only Gcc as a recpient instead of
using your function and killing it. (See the variable
message-allow-no-recipients.)
paul
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-02-09 22:32 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-02-09 6:05 Make nndrafts quit being overly helpful Harry Putnam
2002-02-09 22:32 ` Paul Jarc
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).