From: rintaman@cs.Helsinki.FI (Janne Rinta-Mänty)
Subject: Topic and group parameters
Date: Sun, 13 Jan 2002 19:08:31 +0200 [thread overview]
Message-ID: <m27kqmrxf4.fsf.rintaman.home@mail.cs.helsinki.fi> (raw)
Hello,
The order in which the value of a parameter is determined seems to be
(strongest first):
1. group parameters
2. topic parameters (from deepest to root topic)
3. gnus-parameters (in the order of the list)
...but is it? Experiments with gcc-self (the columns are the values
of gcc-self in group parameters, topic parameters and gnus-parameters
('-' means no value at all); the last column is the value seen in Gcc:
when writing an article in the group (nil means no Gcc header)):
group topic g-p Gcc
"group" "topic" "g-p" "group"
"group" nil "g-p" "group"
"group" - "g-p" "group"
"group" "topic" - "group"
"group" "topic" nil "group"
"group" nil nil "group"
- "topic" "g-p" "topic"
- "topic" nil "topic"
nil "topic" nil nil
nil "topic" - nil
- "topic" - "topic"
nil "topic" "g-p" "g-p" ???
- nil "g-p" "g-p" ???
nil nil "g-p" "g-p" ???
Last three values for Gcc look odd, I was expecting no Gcc header for
those combinations.
Also, I think that gnus-parameters should be stronger than topic
parameters. The manual says in <info://Gnus/Topic+Parameters> "Group
parameters (of course) override topic parameters [...]", and
gnus-parameters has group parameters, only in a different place than
the "real" group parameters.
--
Janne Rinta-Mänty
next reply other threads:[~2002-01-13 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-13 17:08 Janne Rinta-Mänty [this message]
2002-01-15 10:48 ` Janne Rinta-Mänty
2002-01-19 22:22 ` Lars Magne Ingebrigtsen
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=m27kqmrxf4.fsf.rintaman.home@mail.cs.helsinki.fi \
--to=rintaman@cs.helsinki.fi \
/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).