Re: Excessive nntp reads since today

[Tassilo Horn <tsdh@gnu.org>]

Lars Ingebrigtsen <larsi@gnus.org> writes:

>> Then the docs were wrong:
>>
>> ,----[ C-h v gnus-fetch-old-headers RET ]
>> | gnus-fetch-old-headers is a variable defined in `gnus-sum.el'.
>> | 
>> | Documentation:
>> | [...] If it has the value `some', all old headers will be fetched but
>> | only enough headers to connect otherwise loose threads will be
>> | displayed. [...]
>> `----
>>
>> Wolfgang fixed the implementation to reflect exactly what the docs say.
>> IMHO, we'd better have fixed the docs and let the implementation as it
>> has been.
>
> Yeah, but that's after the clarification.  :-)  They used to say:
>
> -displayed in the Summary buffer.  If this variable is t, Gnus
> -will attempt to grab the headers to the old articles, and thereby
> -build complete threads.  If it has the value `some', only enough
> -headers to connect otherwise loose threads will be displayed.  This
> -variable can also be a number.  In that case, no more than that number
> -of old headers will be fetched.  If it has the value `invisible', all
>
> i.e., it didn't say that all headers would be fetched...

Oh, Wolfgang, you prankster. ;-)

So what now?  For what it's worth, I'm for reverting that commit and
clarifying the docs that 'some won't be able to fill loose threads in
case it references articles for which no headers have been fetched.  But
that's not much on an issue: over time, you'll have all headers for the
active threads, just not for very old ones.

Bye,
Tassilo