Re[2]: execline: forbacktickx -x 0 behavior

[Laurent Bercot]

 Now _that_ is an interesting race that I never hit before.
 (It actually has nothing to do with the first eltest; it exits because
the first subprocess from forbacktickx, the first printf, dies late,
during the loop, and its death triggers a spurious test of the exit
conditions, which I failed to guard against.) Thanks for the report!

 Does the current execline git head fix it for you?

--
 Laurent