From: johnsu01 <x@x.x>
Subject: Re: Editing from Draft
Date: Wed, 11 May 2005 17:59:50 -0400 [thread overview]
Message-ID: <87mzr11l0p.fsf@ashbery.wjsullivan.net> (raw)
In-Reply-To: <v9zmv3dmrd.fsf@marauder.physik.uni-ulm.de>
Reiner Steib <reinersteib+from-uce@imap.cc> writes:
> On Tue, May 10 2005, Phillip Lord wrote:
>
>> If I run M-x gnus-draft-mode in the drafts summary buffer then all works
>> correctly
>
> The group somehow lost it's draft property. Ah, we already have something in
> the manual (probably not in 5.9, [1]) about this problem:
>
> ,----[ (info "(gnus)Drafts") ]
> | If the group doesn't exist, it will be created and you'll be subscribed to
> | it. The only way to make it disappear from the Group buffer is to
> | unsubscribe it. The special properties of the draft group comes from a group
> | property (*note Group Parameters::), and if lost the group behaves like any
> | other group. This means the commands below will not be available. To
> | restore the special properties of the group, the simplest way is to kill the
> | group, using `C-k', and restart Gnus. The group is automatically created
> | again with the correct parameters. The content of the group is not lost.
> `----
>
> Bye, Reiner.
Wow, that's a good tip. I've been wondering about this for some time. I have
always just been manually starting gnus-draft-mode before editing a draft.
I wonder how the property got lost, though. I don't think I have ever done
anything to edit the properties of the draft group, and I definitely did not
create it by hand.
--
-johnsu01
-http://www.wjsullivan.net
-GPG Key: AE8600B6
next prev parent reply other threads:[~2005-05-11 21:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 17:27 Phillip Lord
2005-05-10 6:44 ` Reiner Steib
2005-05-10 12:52 ` Phillip Lord
2005-05-10 17:16 ` Reiner Steib
2005-05-11 21:59 ` johnsu01 [this message]
2005-05-12 8:09 ` Reiner Steib
2005-05-12 13:30 ` johnsu01
2005-05-12 21:54 ` Peter TB Brett
2005-05-13 11:59 ` Phillip Lord
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=87mzr11l0p.fsf@ashbery.wjsullivan.net \
--to=x@x.x \
/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).