Drafts feature-request/bug.

[Scott A Crosby <scrosby@cs.rice.edu>]

Hello... Thanks everyone to your help.. I'm still getting used to
gnus... And using a meat axe where subtlety is enough.. Anyways, I've
got a couple comments on drafts..

I like to use drafts a lot. Many times I'll sleep on an email and send
it a day later. Or, I'll check a different message then go back to
editing my current composition. I used to use PINE, and comparing it
to gnus doesn't complement GNUS very much.

First, can I make my drafts group be an ordinary group in the NNML
backend, or must it be in the nndraft backend?

Second, for NNML groups, if I move a message into an NNML group, I
don't have to refresh by pushing 'g' in the group buffer for them to
appear in their new summary buffers. I can go there directly and they
appear. However, for drafts, if I suspend writing a moment 'C-c C-d',
I must refresh the group buffer before I can continue see the message
in the draft group, before I can continue editing that message. This
is slow and annoying.

Third, drafts seem to have a fixed date on them. Usually December
31. It'd be nice if they got updated with the date of the last edit to
them. (IE, just before being edited or sent, update the date header.)

From reading the gnus-agent backend, apparently drafts does
double-duty and also is used to hold the outgoing messages. Thats
incompatible with using them to hold suspended messages. Is there any
easy way of splitting it into the 2 groups?

Thanks.... Scott