GNU Info
(gnus)Group Parameters
Group Parameters
================
The group parameters store information local to a particular group.
Here's an example group parameter list:
((to-address . "ding@gnus.org")
(auto-expire . t))
We see that each element consists of a "dotted pair"--the thing
before the dot is the key, while the thing after the dot is the value.
All the parameters have this form _except_ local variable specs, which
are not dotted pairs, but proper lists.
The following group parameters can be used:
`to-address'
Address used by when doing followups and new posts.
(to-address . "some@where.com")
This is primarily useful in mail groups that represent closed
mailing lists--mailing lists where it's expected that everybody
that writes to the mailing list is subscribed to it. Since using
this parameter ensures that the mail only goes to the mailing list
itself, it means that members won't receive two copies of your
followups.
Using `to-address' will actually work whether the group is foreign
or not. Let's say there's a group on the server that is called
`fa.4ad-l'. This is a real newsgroup, but the server has gotten
the articles from a mail-to-news gateway. Posting directly to this
group is therefore impossible--you have to send mail to the mailing
list address instead.
Some parameters have corresponding customizable variables, each of
which is an alist of regexps and values.
`to-list'
Address used when doing `a' in that group.
(to-list . "some@where.com")
It is totally ignored when doing a followup--except that if it is
present in a news group, you'll get mail group semantics when
doing `f'.
If you do an `a' command in a mail group and you have neither a
`to-list' group parameter nor a `to-address' group parameter, then
a `to-list' group parameter will be added automatically upon
sending the message if `gnus-add-to-list' is set to `t'.
If you do an `a' command in a mail group and you don't have a
`to-list' group parameter, one will be added automatically upon
sending the message.
See also `gnus-parameter-to-list-alist'.
`visible'
If the group parameter list has the element `(visible . t)', that
group will always be visible in the Group buffer, regardless of
whether it has any unread articles.
`broken-reply-to'
Elements like `(broken-reply-to . t)' signals that `Reply-To'
headers in this group are to be ignored. This can be useful if
you're reading a mailing list group where the listserv has inserted
`Reply-To' headers that point back to the listserv itself. This is
broken behavior. So there!
`to-group'
Elements like `(to-group . "some.group.name")' means that all
posts in that group will be sent to `some.group.name'.
`newsgroup'
If you have `(newsgroup . t)' in the group parameter list, Gnus
will treat all responses as if they were responses to news
articles. This can be useful if you have a mail group that's
really a mirror of a news group.
`gcc-self'
If `(gcc-self . t)' is present in the group parameter list, newly
composed messages will be `Gcc''d to the current group. If
`(gcc-self . none)' is present, no `Gcc:' header will be
generated, if `(gcc-self . "string")' is present, this string will
be inserted literally as a `gcc' header. This parameter takes
precedence over any default `Gcc' rules as described later (Note:
Archived Messages).
`auto-expire'
If the group parameter has an element that looks like `(auto-expire
. t)', all articles read will be marked as expirable. For an
alternative approach, Note: Expiring Mail.
`total-expire'
If the group parameter has an element that looks like
`(total-expire . t)', all read articles will be put through the
expiry process, even if they are not marked as expirable. Use with
caution. Unread, ticked and dormant articles are not eligible for
expiry.
See also `gnus-total-expirable-newsgroups'.
`expiry-wait'
If the group parameter has an element that looks like `(expiry-wait
. 10)', this value will override any `nnmail-expiry-wait' and
`nnmail-expiry-wait-function' when expiring expirable messages.
The value can either be a number of days (not necessarily an
integer) or the symbols `never' or `immediate'.
`score-file'
Elements that look like `(score-file . "file")' will make `file'
into the current score file for the group in question. All
interactive score entries will be put into this file.
`adapt-file'
Elements that look like `(adapt-file . "file")' will make `file'
into the current adaptive file for the group in question. All
adaptive score entries will be put into this file.
`admin-address'
When unsubscribing from a mailing list you should never send the
unsubscription notice to the mailing list itself. Instead, you'd
send messages to the administrative address. This parameter
allows you to put the admin address somewhere convenient.
`display'
Elements that look like `(display . MODE)' say which articles to
display on entering the group. Valid values are:
`all'
Display all articles, both read and unread.
`default'
Display the default visible articles, which normally includes
unread and ticked articles.
`comment'
Elements that look like `(comment . "This is a comment")' are
arbitrary comments on the group. They are currently ignored by
Gnus, but provide a place for you to store information on
particular groups.
`charset'
Elements that look like `(charset . iso-8859-1)' will make
`iso-8859-1' the default charset; that is, the charset that will be
used for all articles that do not specify a charset.
See also `gnus-group-charset-alist'.
`ignored-charsets'
Elements that look like `(ignored-charsets x-known iso-8859-1)'
will make `iso-8859-1' and `x-unknown' ignored; that is, the
default charset will be used for decoding articles.
See also `gnus-group-ignored-charsets-alist'.
`posting-style'
You can store additional posting style information for this group
only here (Note: Posting Styles). The format is that of an
entry in the `gnus-posting-styles' alist, except that there's no
regexp matching the group name (of course). Style elements in
this group parameter will take precedence over the ones found in
`gnus-posting-styles'.
For instance, if you want a funky name and signature in this group
only, instead of hacking `gnus-posting-styles', you could put
something like this in the group parameters:
(posting-style
(name "Funky Name")
(signature "Funky Signature"))
`banner'
An item like `(banner . "regex")' causes any part of an article
that matches the regular expression "regex" to be stripped.
Instead of "regex", you can also use the symbol `signature' which
strips the last signature or any of the elements of the alist
`gnus-article-banner-alist'.
`(VARIABLE FORM)'
You can use the group parameters to set variables local to the
group you are entering. If you want to turn threading off in
`news.answers', you could put `(gnus-show-threads nil)' in the
group parameters of that group. `gnus-show-threads' will be made
into a local variable in the summary buffer you enter, and the
form `nil' will be `eval'ed there.
This can also be used as a group-specific hook function, if you
like. If you want to hear a beep when you enter a group, you
could put something like `(dummy-variable (ding))' in the
parameters of that group. `dummy-variable' will be set to the
result of the `(ding)' form, but who cares?
Use the `G p' or the `G c' command to edit group parameters of a
group. (`G p' presents you with a Lisp-based interface, `G c' presents
you with a Customize-like interface. The latter helps avoid silly Lisp
errors.) You might also be interested in reading about topic
parameters (Note: Topic Parameters).
automatically generated by info2www version 1.2.2.9