Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Tassilo Horn <heimdall@uni-koblenz.de>
Subject: Gnus fetches too many headers WAS: Re: Showing Complete Active Threads
Date: Thu, 09 Mar 2006 12:31:27 +0100	[thread overview]
Message-ID: <87mzfzg8hc.fsf_-_@baldur.nicundtas.de> (raw)
In-Reply-To: <lzy7zku0dy.fsf@null.nullsome.net>

Rolleston <Nemo@nullsome.net> writes:

> It attempts to download every header it can from the news server. Try that
> on 'alt.test' and you'll begin to see why (setq gnus-fetch-old-headers t)
> is a bad idea. :)

Ok, I was able to reproduce this. I've set nntp-record-commands to t and
made `g' in Summary Buffer to fetch new articles which resulted in

     infko.general (3)

When I entered this Group Gnus started to fetch several megabytes and
the output in *nntp-log* was

,----[ *nntp-log* after entering infko.general with 3 new articles ]
| 20060309T121041.752 news.uni-koblenz.de GROUP infko.general
| 20060309T121041.926 news.uni-koblenz.de XOVER 1-61172
`----

This newsgroup has medium traffic and I enter it several times a day, so
all except the 3 new articles should have been available...

After the `g' I also had

      comp.emacs (1)

and entering this group resulted in

,----[ *nntp-log* after entering comp.emacs with 1 new article ]
| 20060309T121028.368 news.uni-koblenz.de GROUP comp.emacs
| 20060309T121028.372 news.uni-koblenz.de XOVER 54834-54834
`----

That looks quite ok to me.

So why does Gnus fetch all headers of infko.general but only the needed
headers for comp.emacs?

INFO: I use Gnus with gnus-agent and try to prevent loose threads with

        (setq gnus-fetch-old-headers 'some)

      But the 3 new articles in infko.general don't reference old
      articles which would require the fetching of all headers.

Regards,
Tassilo

  parent reply	other threads:[~2006-03-09 11:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-08  6:07 Rolleston
2006-03-08  8:38 ` Tassilo Horn
2006-03-08 18:53   ` Rolleston
2006-03-08 19:43     ` Tassilo Horn
2006-03-08 20:50       ` Rolleston
2006-03-08 22:45         ` Tassilo Horn
2006-03-12 23:04           ` Rolleston
2006-03-09 11:31         ` Tassilo Horn [this message]
2006-05-14 15:43           ` Gnus fetches too many headers WAS: " Dale Worley
2006-05-14 18:33             ` Tassilo Horn
2006-05-15  7:07               ` Frank Schmitt
2006-05-15  7:48               ` Tassilo Horn
2006-03-15  0:48       ` Matt Ford
2006-03-15  1:08         ` Matt Ford

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=87mzfzg8hc.fsf_-_@baldur.nicundtas.de \
    --to=heimdall@uni-koblenz.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).