From: asjo@koldfront.dk (Adam Sjøgren)
To: info-gnus-english@gnu.org
Subject: Re: How to prevent gnus from always downloading full index
Date: Tue, 19 Jan 2016 12:32:23 +0100 [thread overview]
Message-ID: <87h9i9x0s8.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <6kziw2ikh8.fsf@shaula.iup.uni-bremen.de>
Andreas writes:
>> How many articles do you ask Gnus to display when entering a group?
> 200
I think it should only fetch the "overview" for the newest 200 then. Odd.
>> Have you "caught up" the groups in question (i.e. marked all the old
>> articles as read)?
> Yes, the *group* buffer shows e.g. 2 unread messages for that group.
Then it should only fetch 2 when you enter the group.
>> What does your configuration look like?
>
> I'm using spacemacs, so the base config is at
>
> https://github.com/syl20bnr/spacemacs/blob/master/layers/%2Bemail/gnus/packages.el
Ah! This looks suspicious:
gnus-fetch-old-headers t
From the documentation:
"This feature can seriously impact performance it ignores all locally
cached header entries. Setting it to t for groups for a server that
doesn't expire articles (such as news.gmane.org), leads to very slow
summary generation."
I have nil here. I'm pretty sure this is the culprit.
Setting this twice seems odd:
gnus-keep-backlog 'nil
gnus-keep-backlog '0
I have it set to 20. I think 'nil and '0 are weird values to use - nil
or 0 would make more sense, but keeping the default 20 maybe even more :-)
Best regards,
Adam
--
"It's like somebody with obsessive-compulsive Adam Sjøgren
disorder constantly rearranging the names to fit asjo@koldfront.dk
into some sort of perfect ontology they have in
their heads."
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2016-01-19 11:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 21:41 Andreas Hilboll
2016-01-18 21:56 ` Adam Sjøgren
2016-01-18 22:36 ` Andreas Hilboll
2016-01-19 4:58 ` Eric Abrahamsen
2016-01-19 11:32 ` Adam Sjøgren [this message]
2016-01-19 16:47 ` Andreas Hilboll
2016-01-19 19:32 ` Adam Sjøgren
2016-01-20 1:44 ` B.V. Raghav
2016-01-20 5:17 ` Adam Sjøgren
2016-01-21 13:38 ` B.V. Raghav
2016-01-21 15:57 ` Adam Sjøgren
2016-01-24 10:09 ` Andreas Hilboll
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=87h9i9x0s8.fsf@tullinup.koldfront.dk \
--to=asjo@koldfront.dk \
--cc=info-gnus-english@gnu.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).