From: "Jochen Küpper" <jochen-+It19tn3Rl9sbm7dSapR3bNAH6kLmebB@public.gmane.org>
Subject: Re: gnus-parameters and (visible . t) problem
Date: Fri, 24 Jun 2005 00:13:32 +0200 [thread overview]
Message-ID: <m3fyv8g1rn.fsf@doze.jochen-kuepper.de> (raw)
In-Reply-To: <9e7jglikx6.fsf-G2iyDNEOhahHYNAXZw2rCoRsZ6cCL1yJ@public.gmane.org> (Jochen =?iso-8859-1?Q?K=FCpper's?= message of "Thu, 23 Jun 2005 09:36:53 +0200")
> bojohan+news-dtrdnu4G8ymci/EUP2OQSw@public.gmane.org (Johan Bockgård) writes:
[...correctly points out gnus-permanently-visible-groups...]
So what;s about the following documentaiton-enhancement?
Greetings,
Jochen
--
Einigkeit und Recht und Freiheit http://www.Jochen-Kuepper.de
Liberté, Égalité, Fraternité GnuPG key: CC1B0B4D
(Part 3 you find in my messages before fall 2003.)
Index: texi/gnus.texi
===================================================================
RCS file: /usr/local/cvsroot/gnus/texi/gnus.texi,v
retrieving revision 7.95
diff -u -u -r7.95 gnus.texi
--- texi/gnus.texi 30 Mar 2005 08:17:03 -0000 7.95
+++ texi/gnus.texi 23 Jun 2005 22:09:04 -0000
@@ -2764,6 +2764,9 @@
that group will always be visible in the Group buffer, regardless
of whether it has any unread articles.
+This parameter cannot be set via @code{gnus-parameters}. See
+@code{gnus-permanently-visible-groups} as an alternative.
+
@item broken-reply-to
@cindex broken-reply-to
Elements like @code{(broken-reply-to . t)} signals that @code{Reply-To}
@@ -3055,7 +3058,8 @@
@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
+But some variables, such as @code{visible}, have no effect (For this
+case see @code{gnus-permanently-visible-groups} as an alternative.). For
example:
@lisp
next prev parent reply other threads:[~2005-06-23 22:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.862.1119477929.2857.help-gnu-emacs@gnu.org>
[not found] ` <yoijaclhvmdy.fsf@linus003.dd.chalmers.se>
[not found] ` <yoijaclhvmdy.fsf-PkldqKSsTwjY3LeWNvTtSq/VBoQUuTN+@public.gmane.org>
2005-06-23 7:36 ` Jochen Küpper
2005-06-23 14:40 ` Johan Bockgård
[not found] ` <9e7jglikx6.fsf-G2iyDNEOhahHYNAXZw2rCoRsZ6cCL1yJ@public.gmane.org>
2005-06-23 22:13 ` Jochen Küpper [this message]
2005-06-23 23:47 ` RISKO Gergely
2005-06-26 6:08 ` remote Maildir and IMAP Janusz S. Bień
2005-06-26 13:01 ` Ted Zlatanov
2005-06-26 14:43 ` j.bien
2005-06-26 14:48 ` Janusz S. Bień
2005-06-29 14:42 ` Ted Zlatanov
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=m3fyv8g1rn.fsf@doze.jochen-kuepper.de \
--to=jochen-+it19tn3rl9sbm7dsapr3bnah6klmebb@public.gmane.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).