Date:Tue, 30 Mar 2021 07:33:08 +0300
From:=?UTF-8?B?T8SfdXo=?=
Message-ID:
| The same goes for the job table right?
Yes, though there's no posix explanation for that (no expectation
there that code would ever want to examine it).
| None of ash derivatives (inc
29 Mart 2021 Pazartesi tarihinde Robert Elz yazdı:
> Date:Mon, 29 Mar 2021 17:31:23 +0200
> From:Valentin Lab
> Message-ID: <604a4dab-afc5-cd5e-ee80-64d3dfb2e...@kalysto.org>
>
>
> | In 4.3, this makes sense to me. EXIT trap is not available and not
> executed.
>
Date:Mon, 29 Mar 2021 17:31:23 +0200
From:Valentin Lab
Message-ID: <604a4dab-afc5-cd5e-ee80-64d3dfb2e...@kalysto.org>
| In 4.3, this makes sense to me. EXIT trap is not available and not executed.
|
| In >4.3, I don't understand: 'trap -p' is displaying a trap
29 Mart 2021 Pazartesi tarihinde Valentin Lab
yazdı:
> Hi,
>
> I have encountered an issue when running some bash code from 4.3 that
> behave in an unexpected way on 4.4 or 5 ... I've managed to pinpoint the
> exact issue on my end.
>
> Here is the code:
>
>
> ##
> trap -- 'echo
Hi,
I have encountered an issue when running some bash code from 4.3 that
behave in an unexpected way on 4.4 or 5 ... I've managed to pinpoint the
exact issue on my end.
Here is the code:
##
trap -- 'echo bar' EXIT
(
echo -n 'Subshell TRAP EXIT: '
trap -p EXIT
echo
)
