From: "Jochen Küpper" <jochen-+It19tn3Rl9sbm7dSapR3bNAH6kLmebB@public.gmane.org>
Subject: Re: gnus-parameters limitations
Date: Mon, 03 Jan 2005 18:44:58 +0100 [thread overview]
Message-ID: <9ept0mmmp1.fsf@gowron.rz-berlin.mpg.de> (raw)
In-Reply-To: <v93bzubpf6.fsf-WZbs9ZYJ0ya4nSHvGpykACzlmkwuQ7VwhC4ANOJQIlc@public.gmane.org> (Reiner Steib's message of "Sun, 31 Oct 2004 21:31:09 +0100")
Sorry for the late response, somehow got out of sight. The followup
might be useful for someone looking through the archives.
Reiner Steib <reinersteib+gmane-ZTO5kqT2PaM@public.gmane.org> writes:
> On Sun, Oct 31 2004, Jochen Küpper wrote:
>
>> 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?
[...]
> Are you sure that it doesn't work?
[...Shows working example...]
Ok, it just works!
My problem was that I put postings-styles into gnus-parameters
,----
| (setq gnus-parameters '(("some/group$"
| (posting-style
| (eval (jk/ispell-dutch))))
| ("some"
| (posting-style
| (body "Hoi,\n\n\nGroeten,\nJochen")))))
`----
and expected "hierarchical evaluation" of these... I can see the logic
behind this *not* working and reverted to the use of
gnus-posting-styles, so I get what I want.
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.)
prev parent reply other threads:[~2005-01-03 17:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-31 13:00 Jochen Küpper
2004-10-31 20:31 ` Reiner Steib
[not found] ` <v93bzubpf6.fsf-WZbs9ZYJ0ya4nSHvGpykACzlmkwuQ7VwhC4ANOJQIlc@public.gmane.org>
2005-01-03 17:44 ` Jochen Küpper [this message]
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=9ept0mmmp1.fsf@gowron.rz-berlin.mpg.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).