Hi,
On 2024-03-24 00:57:26 +0100, Gioele Barabucci wrote:
> this issue does not seem to affect version 5.0-6 and later of bash.
>
> $ ! true &
> [1] 2264193
> [1]+ Done true
> $ echo $?
> 0
>
> Please reopen this bug if you can still reproduce this issue.
I confirm that this is now correct. Moreover, in the
/usr/share/doc/bash/changelog.gz file:
This document details the changes between this version, bash-4.4-alpha, and
the previous version, bash-4.3-release.
[...]
jj. Asynchronous commands now always set $? to 0 and are not affected by
whether or not the command's exit status is being inverted.
which corresponds to this bug (I had reported the bug upstream,
see the "Forwarded" URL, and it got fixed at that time).
So it was fixed in bash 4.4.
--
Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
