From: Tassilo Horn <tassilo@member.fsf.org>
To: ding@gnus.org
Subject: Re: how gnus-parameter works when several regexps match
Date: Fri, 11 Feb 2011 09:26:27 +0100 [thread overview]
Message-ID: <871v3fnfik.fsf@member.fsf.org> (raw)
In-Reply-To: <m27hd7pmnv.fsf@gmail.com> (Francis Moreau's message of "Thu, 10 Feb 2011 23:09:08 +0100")
Francis Moreau <francis.moro@gmail.com> writes:
Hi Francis,
first of all, till some months ago, there was a difference in the
handling of (foo . bar) parameters and (foo val) variables. In fact,
one of them would override values from groups matched before and the
others did not. Lars fixed that some time ago, so you should be sure
that your Gnus version is pretty new.
> But, it doesn't work for me (trademark. It's a long story between Gnus
> and me, you know).
>
> For example doing this:
>
> (setq gnus-parameters '(
> ("nnimap\\+foo:INBOX"
> (gcc-self . t)
> (posting-style
> (name "toto")
> (address "titi@foo.com")))
>
> ("nnimap\\+foo"
> (display . [not expire])
> (gnus-large-newsgroup 1000))))
>
> In this case I expect to have name set to 'toto' and adress set to
> 'titi@foo.com' in my INBOX group. However they are not. I think they
> are set to user-full-name and user-mail-address values.
Hm, I've never tried mixing posting-styles in the gnus-parameters...
What if you swap the groups. At least I have my posting-styles and
gnus-parameters configured starting with lax regexps (matching whole
backends, or at least servers), and following regexps match only some
groups to override some general parameters.
> They are set to the expected values only if I comment the second rule
> like the following:
>
> (setq gnus-parameters '(
> ("nnimap\\+foo:INBOX"
> (gcc-self . t)
> (posting-style
> (name "toto")
> (address "titi@foo.com")))))
>
> ; ("nnimap\\+foo"
> ; (display . [not expire])
> ; (gnus-large-newsgroup 1000))))
> ;
>
> Do you have any idea why I get this behaviour ?
I think that pretty much looks like the issue I described at the start
of my mail. So you probably need a newer Gnus version.
Oh, btw, gcc-ing is broken in the current gnus head. Currently, I use
revision
0bca1908b8a435b5ade1dbebeb9f98207e81d9c4
which works for me.
Bye,
Tassilo
next prev parent reply other threads:[~2011-02-11 8:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 12:04 Francis Moreau
2011-02-10 13:05 ` Tassilo Horn
2011-02-10 22:09 ` Francis Moreau
2011-02-11 8:26 ` Tassilo Horn [this message]
2011-02-11 10:45 ` Francis Moreau
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=871v3fnfik.fsf@member.fsf.org \
--to=tassilo@member.fsf.org \
--cc=ding@gnus.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).