Gnus development mailing list
 help / color / mirror / Atom feed
From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: newsgroup variables
Date: 25 Apr 2000 15:22:32 +0200	[thread overview]
Message-ID: <rjem7uz55z.fsf@zuse.dina.kvl.dk> (raw)
In-Reply-To: Shenghuo ZHU's message of "24 Apr 2000 13:04:07 -0400"

Shenghuo ZHU <zsh@cs.rochester.edu> writes:

> 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.

Yes, but you are also supposed to be able to set ordinary variables
with the group parameters mechanism:

Gnus> `(VARIABLE FORM)'
Gnus>      You can use the group parameters to set variables local to the
Gnus>      group you are entering.  If you want to turn threading off in
Gnus>      `news.answers', you could put `(gnus-show-threads nil)' in the
Gnus>      group parameters of that group.  `gnus-show-threads' will be made
Gnus>      into a local variable in the summary buffer you enter, and the form
Gnus>      `nil' will be `eval'ed there.
Gnus> 
Gnus>      This can also be used as a group-specific hook function, if you'd
Gnus>      like.  If you want to hear a beep when you enter a group, you could
Gnus>      put something like `(dummy-variable (ding))' in the parameters of
Gnus>      that group.  `dummy-variable' will be set to the result of the
Gnus>      `(ding)' form, but who cares?



  parent reply	other threads:[~2000-04-25 13:22 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
2000-04-25 13:22     ` Per Abrahamsen [this message]
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=rjem7uz55z.fsf@zuse.dina.kvl.dk \
    --to=abraham@dina.kvl.dk \
    /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).