From: rintaman@cs.Helsinki.FI (Janne Rinta-Mänty)
Subject: Re: group and topic parameters (was: nnimap against Cyrus imapd just stopped working)
Date: Fri, 12 Jul 2002 03:49:55 +0300 [thread overview]
Message-ID: <m21ya9py6k.fsf.rintaman.home@mail.cs.helsinki.fi> (raw)
In-Reply-To: <v9n0synmf0.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Thu, 11 Jul 2002 20:34:43 +0200")
Reiner Steib 2002-07-11T18:34:43Z:
> On Thu, Jul 11 2002, Kai Großjohann wrote:
>> Reiner Steib <4uce.02.r.steib@gmx.net> writes:
>>> - Setting topic parameters via `gnus-parameters'. [...]
I think it would be clearer to have a different alist for topics.
>> Hm. If you find somebody to write it :-)
> That would be nice to have. IMHO having a variable for group
> parameters, but none for topic parameters is a somehow inconsistent.
<AOL>Me too!</AOL>
That somebody who writes it might also want to answer the question in
<URL:http://www.gnus.org/list-archives/ding/200201/msg00912.html>
namely, is the current precedence of parameters good or not.
Now it is
1. group parameters
2. topic parameters
3. gnus-parameters
Where would the new gnus-topic-parameters (or something) go? I had a
look at this in January and this became the biggest problem. IIRC it
would be very easy to get the new topic parameter variable between 2
and 3. But then the precedence order of group and topic parameters in
variables would be different from the "real" parameters. It would be
a mess when moving the "real" parameters to .gnus.
IMHO a more natural (and consistent with the manual) order would be
1. group parameters
2. gnus-parameters
3. topic parameters
and the gnus-topic-parameters-to-be variable would be number 4.
--
Janne Rinta-Mänty
next prev parent reply other threads:[~2002-07-12 0:49 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 20:10 nnimap against Cyrus imapd just stopped working Steinar Bang
2002-07-09 20:20 ` Simon Josefsson
2002-07-09 20:34 ` Steinar Bang
2002-07-09 20:38 ` Steinar Bang
2002-07-09 20:44 ` Simon Josefsson
2002-07-09 20:55 ` Steinar Bang
2002-07-09 21:04 ` Simon Josefsson
2002-07-09 21:51 ` Steinar Bang
2002-07-10 11:02 ` Simon Josefsson
2002-07-10 11:12 ` Steinar Bang
2002-07-09 21:53 ` Steinar Bang
2002-07-10 5:58 ` Steinar Bang
2002-07-09 20:41 ` Simon Josefsson
2002-07-09 20:50 ` Steinar Bang
2002-07-09 21:02 ` Simon Josefsson
2002-07-09 21:43 ` Steinar Bang
2002-07-10 11:05 ` Simon Josefsson
2002-07-10 11:17 ` Steinar Bang
2002-07-10 11:26 ` Simon Josefsson
2002-07-10 11:43 ` Steinar Bang
2002-07-10 12:39 ` Kai Großjohann
2002-07-10 14:21 ` Reiner Steib
2002-07-11 8:18 ` Kai Großjohann
2002-07-11 18:34 ` group and topic parameters (was: nnimap against Cyrus imapd just stopped working) Reiner Steib
2002-07-12 0:49 ` Janne Rinta-Mänty [this message]
2002-07-10 22:34 ` nnimap against Cyrus imapd just stopped working Steinar Bang
2002-07-11 10:37 ` A .newsrc.eld validator? (Was: nnimap against Cyrus...) Steinar Bang
2002-07-11 16:45 ` nnimap against Cyrus imapd just stopped working Steinar Bang
2002-07-11 17:56 ` Steinar Bang
2002-07-11 18:09 ` Steinar Bang
2002-07-11 18:17 ` Steinar Bang
2002-07-11 18:51 ` Steinar Bang
2002-07-26 12:18 ` Simon Josefsson
2002-07-27 9:38 ` Steinar Bang
2002-07-11 20:01 ` Steinar Bang
2002-07-11 22:24 ` Amos Gouaux
2002-07-11 22:33 ` Amos Gouaux
2002-07-12 5:54 ` Steinar Bang
2002-07-10 8:50 ` Kai Großjohann
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=m21ya9py6k.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).