From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: reading nntp+quimby:gnus.gnus-bug
Date: 11 Aug 2000 15:25:46 +0200 [thread overview]
Message-ID: <vaflmy4nd45.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "10 Aug 2000 22:32:36 +0200"
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.
prev parent reply other threads:[~2000-08-11 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-28 15:30 Kai Großjohann
2000-08-10 20:32 ` Lars Magne Ingebrigtsen
2000-08-11 13:25 ` Kai Großjohann [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=vaflmy4nd45.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.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).