Re: nwildlsearch regex case, does 'match' not 'search'?
Jeremy Harris via Exim-users <[email protected]>
| Newsgroups | gmane.mail.exim.user |
|---|---|
| Message-ID | <[email protected]> |
On 2025/10/22 2:59 PM, Sander Smeenk via Exim-users wrote:
> It seems that using ${lookup {..}nwildlsearch{myfile}{true}{false}} does
> wat python would call a 'match' instead of a 'search' when using the '^'
> character to indicate the keys are regexps?
> Or rather, the '^' to indicate the key is a regexp, also seems to be
> handled as the Beginning Of Line anchor in regexp lingo.
>
> This isn't made clear in the docs, or did i miss it?
The ^ does remain part of the RE, and hence is an anchor.
The docs could point this out explicitly; I agree it's possible
to not realise it. I'll have a go at that.
I can't comment on Python. Exim is not Python.
--
Cheers,
Jeremy
--
## subscription configuration (requires account):
## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/
## unsubscribe (doesn't require an account):
## [email protected]
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/