From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: On loosing marks in nntp groups...
Date: Mon, 14 May 2007 18:52:21 +0900 [thread overview]
Message-ID: <b4m646vag16.fsf@jpl.org> (raw)
In-Reply-To: <mux3b1zx092.fsf@uzeb.lrde.epita.fr>
>>>>> In <mux3b1zx092.fsf@uzeb.lrde.epita.fr> Didier Verna wrote:
> I'd already reported this problem some time ago, but this morning I
> figured out the cause. I don't have time to look for a fix right now,
> but anybody else is welcome to try :-) In the meantime I just wanted to
> report the origin of the problem back to the list.
> I have a group in which more than 200 articles are ticked. All of them
> are also in the cache (they appear denoted as !* in the summary buffer),
> bit *most* of them are now gone from the server.
> When I enter the summary buffer, gnus-select-newsgroup calls
> gnus-fetch-headers to retrieve the headers for these articles, and gets
> a bunch of "no such article" errors back. One way or another, what's
> left (and saved) in the marks are only the articles still present on the
> server.
> At first sight, gnus-fetch-headers should probably look in the cache
> before actually trying to talk to the server...
`gnus-fetch-headers' calls `gnus-retrieve-headers', which looks
to look in the cache first if `gnus-use-cache' is non-nil and
Gnus knows articles to be fetched. Of course Gnus knows them
that are ticked and cached in such a case. Actually I have such
articles (ticked and cached but expired in the server) but have
no problem. It is because `gnus-use-cache' is `passive' in my
case, maybe.
Regards,
next prev parent reply other threads:[~2007-05-14 9:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-14 8:44 Didier Verna
2007-05-14 9:52 ` Katsumi Yamaoka [this message]
2007-05-14 10:07 ` Didier Verna
2007-07-04 10:03 ` Katsumi Yamaoka
2007-07-04 12:08 ` Didier Verna
2007-05-21 2:30 ` Dan Nicolaescu
2007-05-28 9:55 ` Didier Verna
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=b4m646vag16.fsf@jpl.org \
--to=yamaoka@jpl.org \
--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).