Re: Problem with gnus-parameters

[Tassilo Horn <tassilo@member.fsf.org>]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

Hi Lars,

>> I can live with the current situation.  It's just that I think it's
>> not obvious, and it's not documented.
>
> I've now documented it.

You mean this?

,----[ (info "(gnus)Group Parameters") ]
|    The first clause that matches the group name will be used.
`----

That's actually not true.  In fact, if that was true, then the example
above that sentence would contain "dead code" because "mail\\.me" could
never match because the first clause always wins.

In the current situation, the *last* matching clause defines the group
parameters, and group parameters of previous matches are discarded.  For
group local variables, *all* matching clauses contribute to the final
values, i.e., here we have a cumulative approach (equal to posting
styles), where a latter clause may add to or even override previous
settings.  (I consider this a major advantage.)

That's exactly what I've complained about: the differences in the
evaluation strategy of similar items in the same alist.  Furthermore,
since group local variables in gnus-parameters are handled exactly as
gnus-posting-styles, I don't see a reason why group parameters are
treated as an exception.

If there are technical reasons, that's fine with me.  I can live with
it.  So, please fill in this form:

  - [ ] It'll stay as-is because of reason ________________________.

  - [ ] Oh, I didn't notice it's that awkward.  I'll fix it in a way
        that ______________________________________________________.

In any case, I happily volunteer to clarify the docs.

Bye,
Tassilo