Gnus development mailing list
 help / color / mirror / Atom feed
From: Philipp Haselwarter <philipp.haselwarter@gmx.de>
To: ding@gnus.org
Subject: gnus-fetch-old-headers, big groups and old marks
Date: Thu, 03 Nov 2011 00:35:21 +0100	[thread overview]
Message-ID: <87d3danlmu.fsf@nzebook.haselwarter.org> (raw)

I set gnus-verbose to 10 for some testing and was quite surprised to see
some 4000kB being fetched when I entered gmane.emacs.orgmode .

It seems that when gnus-fetch-old-headers is non-nil it fetches old
headers for ticked messages, which makes it practically unusable for big
groups.  Wouldn't it be nicer if gnus started by fetching "old" headers
for the most recent articles of the group (ie especially the unread
ones) and stop once as many as specified in gnus-fetch-old-headers are
retrieved?
I guess the current strategy is somehow based on the oldest article and
tries to fetch everything with one connection to keep things
efficient. However, for me this strategy means I have to turn this neat
feature off :/
Can you Make It Work™?

-- 
Philipp Haselwarter




             reply	other threads:[~2011-11-02 23:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02 23:35 Philipp Haselwarter [this message]
2011-11-03 22:16 ` Lars Magne Ingebrigtsen
2011-11-04  0:15   ` Philipp Haselwarter

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=87d3danlmu.fsf@nzebook.haselwarter.org \
    --to=philipp.haselwarter@gmx.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).