From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: newsgroup variables
Date: Mon, 24 Apr 2000 20:44:28 +0200 [thread overview]
Message-ID: <200004241844.UAA27063@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Shenghuo ZHU's message of "24 Apr 2000 13:04:07 -0400"
Shenghuo ZHU <zsh@cs.rochester.edu> writes:
> Newsgroup variables are like local variables. They are associated to
> the current "active" group. For example, you want to use
> gnus-use-cache with different values for different groups. But when
> you have two summary buffers at the same time, the second group
> setting may override the first one. It may simply solved by making
> those variables as local variables of the summary buffer,
Yes, that's the way I did it.
> but the article buffer may use the variables also.
Like I said, I think many local variables should be copied all over
the place by Gnus.
> The implementation is just like gnus-newsgroup-name does,
> i.e. replacing the global values with the local values after
> switching to a summary buffer.
Err, hm. I don't know anything about the implementation of
gnus-newsgroup-name, but I'll go look.
> Group parameters are not variables. To access variables, you have to
> call get-parameter functions. And you can not use gnus-use-cache as a
> group parameter.
After typing `G c' in the Group buffer, it is possible to set local
variables in addition to group parameters. I'm not sure what happens
when one does that, though.
> KG> One thing which would be nice is this: some variables are used in
> KG> the summary buffer, others are used in the article buffer, and
> KG> still others are used in the message buffers that are created from
> KG> the summary buffer. Could you do stuff that copies the variables
> KG> over to all these buffers so that the right thing happens?
>
> The variables are not copied to all these buffers, just copied
> globally. Actually, the article buffer has few local variables besides
> gnus-summary-buffer. I can not find that the message buffer has such a
> local variable. Maybe we should make one.
??? I think I'll go read the sources, first. I can't make heads nor
tails of what you're saying :-) Not your fault, of course.
kai
--
Beware of flying birch trees.
next prev parent reply other threads:[~2000-04-24 18:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-24 14:30 Shenghuo ZHU
2000-04-24 16:24 ` Kai Großjohann
2000-04-24 17:04 ` Shenghuo ZHU
2000-04-24 18:44 ` Kai Großjohann [this message]
2000-04-25 13:22 ` Per Abrahamsen
2000-04-26 12:31 ` Janne Rinta-Manty
2000-04-26 12:42 ` Kai Großjohann
2000-04-26 13:39 ` Shenghuo ZHU
2000-04-26 15:58 ` Kai Großjohann
2000-04-26 17:24 ` Shenghuo ZHU
2000-04-26 20:09 ` Kai Großjohann
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=200004241844.UAA27063@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.org \
/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).