On Thu Aug 24 2023 at 07:07 PM +0100, Jeremy Harris via Exim-users wrote:
> > Bother. I didn't spot that $value is documented to be useable as the
> > result after the call, not just in the result expansions.
>
> Addressed by c18090c685f5, 21b172df101c.
Thanks, Jeremy and Andreas!
--
Bill
--
On 23/08/2023 20:46, Jeremy Harris via Exim-users wrote:
This is recent breakage - Checking the uploaded versions this was broken
by either
cf3fecb9e873df38a9245775a3887e73a8716083 Fix free of $value after
${run...}
Bother. I didn't spot that $value is documented to be useable as the
result
On 23/08/2023 16:00, Andreas Metzler via Exim-users wrote:
On 2023-08-23 Andreas Metzler wrote:
On 2023-08-22 Bill Brelsford via Exim-users wrote:
Under Exim 4.96-19 in Debian unstable/testing, ${run fails to put
standard output into $value. E.g., in a .forward file,
[...]
This is recent
On 2023-08-23 Andreas Metzler wrote:
> On 2023-08-22 Bill Brelsford via Exim-users wrote:
>> Under Exim 4.96-19 in Debian unstable/testing, ${run fails to put
>> standard output into $value. E.g., in a .forward file,
[...]
> This is recent breakage - Checking the uploaded versions this was brok
On 2023-08-22 Bill Brelsford via Exim-users wrote:
> Under Exim 4.96-19 in Debian unstable/testing, ${run fails to put
> standard output into $value. E.g., in a .forward file,
> if "${run{/bin/echo -n foo}{}}$runrc" is not 99
> then save /tmp/exim-$runrc-$value endif
> creates file /tmp/
