https://bugs.exim.org/show_bug.cgi?id=1679
--- Comment #18 from Philip Hazel <ph10@???> ---
I do view this as nonsense. *MARK names are processed at compile time into
fixed strings. Using \g in an interpreted name causes an error. Extending
processing of *MARK names, as I have just done, was relatively simple, and I
felt it might be useful in several contexts. Using it for parallel replacements
is a fudge that just happens to work. To do anything more complicated would be
better handled by a different approach.
--
You are receiving this mail because:
You are on the CC list for the bug.
