From: Kai Grossjohann <grossjoh@charly.informatik.uni-dortmund.de>
Cc: ding@ifi.uio.no
Subject: Re: nndraft and "expired" articles
Date: 14 Feb 1996 10:13:57 +0100 [thread overview]
Message-ID: <vafka1qclre.fsf@dusty.informatik.uni-dortmund.de> (raw)
In-Reply-To: jvinson@cheux.ecs.umass.edu's message of 13 Feb 1996 12:33:34 -0500
>>>>> On 13 Feb 1996 12:33:34 -0500, jvinson@cheux.ecs.umass.edu (Jack
>>>>> Vinson) said:
Jack> Shouldn't nndraft treat expired articles just like the other
Jack> back ends? I mean expired articles should not show up in the
Jack> Summary buffer unless I do C-u Ret to enter the group.
nndraft is explicitly set up so that no message is expired, ever.
You'll have to `B DEL' the messages, I'm afraid. Normally, though,
there should only be `interesting' messages in them, anyway (messages
that you have begun writing but not finished).
C-c C-k is supposed to really abort writing a message, I think.
kai
--
Life is hard and then you die.
next prev parent reply other threads:[~1996-02-14 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-02-13 17:33 Jack Vinson
1996-02-14 9:13 ` Kai Grossjohann [this message]
1996-02-14 16:06 ` Lars Magne Ingebrigtsen
1996-02-14 17:52 ` Joe Hildebrand
1996-02-14 18:43 ` Mark Boyns
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=vafka1qclre.fsf@dusty.informatik.uni-dortmund.de \
--to=grossjoh@charly.informatik.uni-dortmund.de \
--cc=ding@ifi.uio.no \
/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).