From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: gnus won't cache articles retrieved with gnus-summary-refer-parent-article (`^')
Date: Wed, 05 Jun 2002 11:34:53 +0200 [thread overview]
Message-ID: <vaflm9u132a.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <87elfn6kce.fsf@richl.jtn>
RL <alcoco@carrotmail.com> writes:
> But how come gnus can't operate on the retrieved messages? For
> caching, couldnt gnus just save the message in a file?
Gnus wants to use the article number as the file name (to make sure
the file name is unique, and to know the order of the messages). If
Gnus doesn't know the article number, it cries bloody murder...
But as those who have no need of a name said, this has been fixed in
Oort Gnus: that version tries to glean the article number from the
Xref header.
kai
--
Silence is foo!
prev parent reply other threads:[~2002-06-05 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87adqcw8y1.fsf@richl.jtn>
[not found] ` <vafn0uc5e70.fsf@lucy.cs.uni-dortmund.de>
2002-06-04 17:10 ` RL
2002-06-05 9:34 ` Kai Großjohann [this message]
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=vaflm9u132a.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).