Re: Fancy Mail Splitting documentation needs improved?

[Kan-Ru Chen <kanru@kanru.info>]

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

> Kan-Ru Chen <kanru@kanru.info> writes:
>>
>> OK, the difference is that with `|' and `&' you have to specify the
>> target SPLIT for every rule.  What in my mind is something like
>> programmable rules.  Ideally it would look like:
>> (if (or (field-match "list-id" "...")
>>         (field-match "list-id" "..."))
>>     (split "mail.list"))
>> Of course this could be done via the `:' operator, but will loose the
>> benefits from field cache.  What to do? I'm pondering...
>
> I'm probably misunderstanding something here, but `|' and `&' in the
> splitting rules (should) work just the same as `or' and `and' in Lisp:
>
> (or 'foo 'bar 'zot)
> => foo
>
> (and nil nil 'foo)
> => nil

So something that analog to `cond' would be very useful.  Multiple
condition that leads to one destination.

- Kanru