From: Reiner Steib <reinersteib+gmane@imap.cc>
To: info-gnus-english@gnu.org
Subject: Group parameters / `gnus-parameters' (was: prompts when moving articles etc)
Date: Tue, 18 Dec 2007 12:48:48 +0100 [thread overview]
Message-ID: <v9zlw89de0.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <8763ywjtno.fsf@member.fsf.org>
On Tue, Dec 18 2007, Tassilo Horn wrote:
> A good place to do this on a group specific way would be
> `gnus-parameters'.
>
> ,----[ (info "(gnus)Group Parameters") ]
> | The group parameters store information local to a particular group.
> `----
>
> Oh, this first message of the docs is not really correct.
I think it is correct because it refers to the group parameters you
set via `G p' or `G c' ...
,----[ (info "(gnus)Group Parameters") ]
| 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::).
`----
... in contrast to the variable `gnus-parameters':
,----[ (info "(gnus)Group Parameters") ]
| Group parameters can be set via the `gnus-parameters' variable too.
`----
> You can store informations local to a group of groups that are
> matched by a given regexp.
Maybe reordering the text and adding a note about `gnus-parameters'
near the beginning of the node would make it more clear?
--8<---------------cut here---------------start------------->8---
--- gnus.texi.~6.603.2.144.~ 2007-12-14 22:43:49.000000000 +0100
+++ gnus.texi 2007-12-18 12:41:52.000000000 +0100
@@ -2717,6 +2717,15 @@
@cindex group parameters
The group parameters store information local to a particular group.
+
+Use the @kbd{G p} or the @kbd{G c} command to edit group parameters of a
+group. (@kbd{G p} presents you with a Lisp-based interface, @kbd{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 (@pxref{Topic Parameters}).
+Additionally, you can set group parameters via the
+@code{gnus-parameters} variable, see below.
+
Here's an example group parameter list:
@example
@@ -3083,12 +3092,6 @@
@end table
-Use the @kbd{G p} or the @kbd{G c} command to edit group parameters of a
-group. (@kbd{G p} presents you with a Lisp-based interface, @kbd{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 (@pxref{Topic Parameters}).
-
@vindex gnus-parameters
Group parameters can be set via the @code{gnus-parameters} variable too.
But some variables, such as @code{visible}, have no effect (For this
--8<---------------cut here---------------end--------------->8---
> @Reiner: Should I fix that in Emacs' CVS (23.0.50) where I have access,
> so that it will be synched after a while?
For doc-fixes, the EMACS_22_BASE branch (or v5-10 in Gnus CVS) would
be more suitable.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2007-12-18 11:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 13:42 prompts when moving articles etc Stein Arild Strømme
2007-12-17 16:35 ` Stein Arild Strømme
2007-12-18 8:26 ` Tassilo Horn
2007-12-18 11:48 ` Reiner Steib [this message]
2007-12-18 18:49 ` Group parameters / `gnus-parameters' Tassilo Horn
2008-02-04 12:12 ` Sébastien Vauban
2008-02-04 18:13 ` verbatim markers (was: Group parameters / `gnus-parameters') Reiner Steib
2007-12-18 11:37 ` prompts when moving articles etc Reiner Steib
2007-12-19 13:10 ` Stein Arild Strømme
[not found] ` <mailman.5150.1197966396.18990.info-gnus-english@gnu.org>
2007-12-18 13:19 ` Stein Arild Strømme
2007-12-18 15:09 ` Tassilo Horn
[not found] ` <mailman.5158.1197991076.18990.info-gnus-english@gnu.org>
2007-12-19 10:20 ` Stein Arild Strømme
2007-12-19 13:36 ` Ted Zlatanov
2007-12-19 13:41 ` Stein Arild Strømme
2007-12-18 13:15 ` Martin Fischer
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=v9zlw89de0.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=info-gnus-english@gnu.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).