Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Reiner Steib <4uce.02.r.steib@gmx.net>
Subject: What is (setq gnus-fetch-old-headers number) supposed to do? (was: Gnus always downloads 19Mb headers)
Date: Thu, 06 Jun 2002 17:38:12 +0200	[thread overview]
Message-ID: <v9vg8w1kpn.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <vaf3cw0ipav.fsf@lucy.cs.uni-dortmund.de>

On Thu, Jun 06 2002, Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai wrote:

> Reiner Steib <4uce.02.r.steib@gmx.net> writes:
>
>> I've experimented with setting it to a number, say N. Then, Gnus only
>> seemed to fetch old headers, if there were less than N articles in
>> this group (total number of articles). But maybe my impression wrong.
>> Is this how it's supposed to work?
>
> I think it's supposed to always fetch N old headers, unless the group
> has less than N articles (then it fetches all headers).

This is what I expected to see, too.

It would be very nice to have something like this (don't know if it's
possible):

1. Fetch unread (and ticked) articles.
2. Look at the References and fetch at most N old (parent-) articles of
   those articles.

> It doesn't make sense for it to fetch no old headers at all in large
> groups.

I switched back to (setq gnus-fetch-old-headers 2000) now. In some
groups (or even some threads?) I see old headers and in others not,
though there should be some very recent parent articles. E.g. here in
gnus.emacs.gnus I see:

  +[  16: Kai Großjohann      ] Re: Gnus always downloads 19Mb headers
O  [  24: Armin Lambacher     ] Re: strange error message with imap
O +  [  11: those who know me ha] 
O      [  17: Armin Lambacher     ] 
O +      [  17: those who know me ha] 
           [  37: Armin Lambacher     ] 
O +  [  24: Simon Josefsson     ] 
O      [ 156: Armin Lambacher     ] 
O +      [  33: Simon Josefsson     ] 
           [  14: Armin Lambacher     ] 
  +[  19: Kai Großjohann      ] Re: nnimap and split with parent
   [  35: Uli Wortmann        ] Re: gnus/nnimap behaviour in case of [...]

I would expect to see (at least some of) the parents of _both_ of your
articles Kai, as the parents are from today, so they definitively are
within the value 2000 of gnus-fetch-old-headers. The highest article
number for g.e.g is around 22162. Changing gnus-fetch-old-headers to
30000 and re-entering the group also didn't show me all expected
parents. I can't see any systematic behavior. :-(

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/


      parent reply	other threads:[~2002-06-06 15:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <871yc00w8b.fsf@gmx.net>
     [not found] ` <acp9je02r3k@enews2.newsguy.com>
     [not found]   ` <871ybylpxs.fsf@gmx.net>
     [not found]     ` <vafelfw1eqr.fsf@lucy.cs.uni-dortmund.de>
2002-06-05 17:09       ` Gnus always downloads 19Mb headers Felix Natter
     [not found]         ` <v94rghs4j4.fsf@marauder.physik.uni-ulm.de>
     [not found]           ` <vaf3cw0ipav.fsf@lucy.cs.uni-dortmund.de>
2002-06-06 15:38             ` Reiner Steib [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=v9vg8w1kpn.fsf@marauder.physik.uni-ulm.de \
    --to=4uce.02.r.steib@gmx.net \
    --cc=reiner.steib@gmx.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).