Unexpected behavior of ${x#word} and ${x/pat/str} in the case command

Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall uname output: Linux x2 5.10.0-35-amd64 #1 SMP Debian 5.10.237-1 (2025-05-19) x86_64 GNU/Linux

Re: set -e doesn't trigger when command substitutions returns, why?

Hello microsuxx,Thank you for the replies.I did some more manual testing, the wait -n builtin looks kinda sketchy because of what the bash manpage of the builtin wait says, during testing I see that wait -n is able to detect that $? has become -1 in the trap handler command, but if the trap han

Re: set -e doesn't trigger when command substitutions returns, why?

On Mon, Jun 23, 2025, at 10:30 PM, nkkralev--- via Bug reports for the GNU Bourne Again SHell wrote: > Hello microsuxx,Thank you for the replies.I did > some more manual testing, the wait -n builtin looks kinda > sketchy because of what the bash manpage of the builtin wait says, > during testin