[exim/exim] Spec, examples of different lookup syntax: if it shouldn't have read as suggested, it should explain why not (Issue #3216)
maeqs5a via Exim-dev <[email protected]> Wed, 15 Apr 2026 00:51:43 +0100
| Newsgroups | gmane.mail.exim.devel |
|---|---|
| Message-ID | <exim/exim/issues/[email protected]> |
Referring to Examples of different lookup syntax ( https://code.exim.org/exim/exim/src/commit/e8a71fcd7027ff383b06bfe715836c32b18eaea2/doc/doc-docbook/spec.xfpt#L6769-L6777 ) , I think it confuses the 1st and 2nd kind. If it shouldn't have read as in
>
>
>
> --- a/doc/doc-docbook/spec.xfpt
> +++ b/doc/doc-docbook/spec.xfpt
> @@ -6768,10 +6768,10 @@ time, be aware that some of it will make a lot
> more sense after you have read
> chapters & CHAPdomhosaddlists>>& and & CHAPexpand>>&.
>
>
>
> .section "Examples of different lookup syntax" "SECID60"
> -It is easy to confuse the two different kinds of lookup, especially as
> the
> -lists that may contain the *second* kind are always expanded before being
>
> -processed as lists. Therefore, they may also contain lookups of the *first*
> kind.
> +It is easy to confuse the two different kinds of lookup, especially as
> +lists that may contain the *first* kind are always expanded before being
> +processed as lists. Therefore, they may also contain lookups of the *second*
> kind.
> Be careful to distinguish between the following two examples:
> .code
> domains = ${lookup{$sender_host_address}lsearch{/some/file}}
> domains = lsearch;/some/file
>
>
then I do believe it should explain why it shouldn't read like that.
To reiterate, doesn't the paragraph that was patched above is reiterated at a concrete example for the possible confusion ( https://code.exim.org/exim/exim/src/commit/e8a71fcd7027ff383b06bfe715836c32b18eaea2/doc/doc-docbook/spec.xfpt#L6812-L6819 ) ?
---
View it on Exim Forgejo ( https://code.exim.org/exim/exim/issues/3216 ) or reply to this email directly.