From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Expiration problem
Date: Wed, 06 Mar 2002 12:32:13 +0100 [thread overview]
Message-ID: <vafzo1m9bk2.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <uvgcaq8xa.fsf@axis.com> (Niklas Morberg's message of "Wed, 06 Mar 2002 11:37:05 +0100")
Niklas Morberg <niklas.morberg@axis.com> writes:
> No. I did try M-u however, which did not work. For a moment
> there I thought that clearing marks restored an article to
> its original state (whatever that is), but it does not
> affect caching status.
No, M-u removes read and unread marks, but "*" is neither a read nor
an unread mark.
kai
--
Silence is foo!
next prev parent reply other threads:[~2002-03-06 11:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-06 8:00 Niklas Morberg
2002-03-06 8:57 ` Kai Großjohann
2002-03-06 10:37 ` Niklas Morberg
2002-03-06 11:32 ` Kai Großjohann
2002-03-06 11:32 ` Kai Großjohann [this message]
2002-03-06 10:37 ` Niklas Morberg
2002-03-06 8:57 ` Kai Großjohann
-- strict thread matches above, loose matches on Subject: below --
2002-03-06 8:00 Niklas Morberg
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=vafzo1m9bk2.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.org \
/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).