Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Tassilo Horn <heimdall@uni-koblenz.de>
Subject: Re: Showing Complete Active Threads
Date: Wed, 08 Mar 2006 23:45:15 +0100	[thread overview]
Message-ID: <87acc0eetg.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. :)

Sometimes I was wondering why Gnus downloads several MBs when the group
only has a few new articles, too.

>> BTW: I use
>>
>>      (setq gnus-fetch-old-headers 'some)
>>
>> which fetches only those old headers needed to prevent loose threads
>> (all old headers till a common parent article is found). That's more
>> concise and expresses this thread's structure as well.
>
> Sounds good. If only it worked! :) 

At least it seems to work here with a fresh CVS Gnus.

> Ok, how about another approach?

Sorry, but that's too advanced for me. First I would try to check if
it's a real bug. Perhaps try setting

     (setq nntp-record-commands t)

which sends nntp-commands to Buffer *nntp-log*. Then you can see which
articles it fetches and see if it acts correctly. Helping to fix a bug
(if it really is one) is much better than working arround it.

Best regards,
Tassilo

  reply	other threads:[~2006-03-08 22:45 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 [this message]
2006-03-12 23:04           ` Rolleston
2006-03-09 11:31         ` Gnus fetches too many headers WAS: " Tassilo Horn
2006-05-14 15:43           ` 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=87acc0eetg.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).