From: "Jochen Küpper" <ml-W2i0oK7yYu0+t3nig+EZI7NAH6kLmebB@public.gmane.org>
Subject: gnus-parameters limitations
Date: Sun, 31 Oct 2004 14:00:14 +0100 [thread overview]
Message-ID: <m31xffoxep.fsf@doze.jochen-kuepper.de> (raw)
I am wondering about some limitations of gnus-parameters, using GNU
Emacs 21.3.1 and No Gnus v0.3.
The manual states (correctly) that some settings cannot be performed
through the gnus-parameters variable:
,----[ (info "(gnus)Group Parameters") ]
| Group parameters can be set via the `gnus-parameters' variable too.
| But some variables, such as `visible', have no effect. For example:
`----
Why is that?
I am sharing my .emacs and .gnus files between computers (using cvs),
so it would be great to put everything into these files. Having to use
Group Parameters (stored in .newsrc.eld) is fairly uncomfortable. But
also generally it would be nice to have everything stored in one
place.
What would be necessary to improve on that?
Apparently the parsing of gnus-parameters is performed so that the
first matching entry is used. Wouldn't it be nice to allow for
hierarchical settings as with posting styles, where all matching
entries are used and later settings overwrite earlier ones?
Assume the following setting
,----
| (setq gnus-parameters
| '(("mail\\..*"
| (gnus-show-threads nil)
| (gnus-use-scoring nil)
| (gcc-self . t)
| (display . all))
| ("mail\\.some\\.group"
| (gnus-use-scoring t)
| (to-group . "\\1"))
`----
I would expect to have the following apply to mail.some.group:
,----
| (gnus-show-threads nil)
| (gcc-self . t)
| (display . all))
| (gnus-use-scoring t)
| (to-group . "\\1"))
`----
Greetings,
Jochen
--
Einigkeit und Recht und Freiheit http://www.Jochen-Kuepper.de
Liberté, Égalité, Fraternité GnuPG key: CC1B0B4D
Sex, drugs and rock-n-roll
next reply other threads:[~2004-10-31 13:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-31 13:00 Jochen Küpper [this message]
2004-10-31 20:31 ` Reiner Steib
[not found] ` <v93bzubpf6.fsf-WZbs9ZYJ0ya4nSHvGpykACzlmkwuQ7VwhC4ANOJQIlc@public.gmane.org>
2005-01-03 17:44 ` Jochen Küpper
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=m31xffoxep.fsf@doze.jochen-kuepper.de \
--to=ml-w2i0ok7yyu0+t3nig+ezi7nah6klmebb@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).