reading nntp+quimby:gnus.gnus-bug

reading nntp+quimby:gnus.gnus-bug

[Kai Großjohann]

Gnus wants to download megabytes of header information when I enter
that group, even if I have set gnus-fetch-old-headers to nil in the
group parameters.

Is there anything I can do to make Gnus download fewer headers?

kai
-- 
Beware of flying birch trees.

Re: reading nntp+quimby:gnus.gnus-bug

[Lars Magne Ingebrigtsen]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Gnus wants to download megabytes of header information when I enter
> that group, even if I have set gnus-fetch-old-headers to nil in the
> group parameters.

Hm...  I think this might be yet another case where the group
parameters is setting stuff in the summary buffer, but the variable is
accessed in a different buffer (in this case, most likely
" *server quimby.gnus.org*" or something like that).  I think.

Does that sound likely?

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

Re: reading nntp+quimby:gnus.gnus-bug

[Kai Großjohann]

On 10 Aug 2000, Lars Magne Ingebrigtsen wrote:

> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> 
>> Gnus wants to download megabytes of header information when I enter
>> that group, even if I have set gnus-fetch-old-headers to nil in the
>> group parameters.
> 
> Hm...  I think this might be yet another case where the group
> parameters is setting stuff in the summary buffer, but the variable
> is accessed in a different buffer (in this case, most likely "
> *server quimby.gnus.org*" or something like that).  I think.
> 
> Does that sound likely?

Yes.

This whole local variables business appears to be rather nasty.  I was
about to suggest a function gnus-create-buffer which copies all local
variables.  But now I see that neither the *Article* buffer nor the
*server foo* buffer are created each time after a group is entered.  Gah!

I don't know what to do...

kai
-- 
I like BOTH kinds of music.