Date: Mon, 18 May 2026 07:51:22 -0400
From: Zachary Santer <[email protected]>
Message-ID:
<cabkljukexqcqzwrtvk63vy3rkjwkh2x2fk4pupbon441hy5...@mail.gmail.com>
| Stan already demonstrated that bash will continue sourcing whatever file.
I did not see that, probably it was only sent to help-bash, to which I
do not subscribe (I don't know bash well enough to help people who have
issues with it, but I do know shells in general well enough to know what
is a bug, and what isn't, at least when it doesn't involve bash extensions).
However, I would consider that to be a simple bug which should be fixed
in the source, not the man page (and a little surprising, as for many
things, sourced files act like functions - no args, etc, but "return"
works.)
But (using your f1 and f2 as in your original message):
jacaranda$ for f in a b c; do f1; done
bash: 1: parameter null or not set
jacaranda$
which makes it clear that isn't just functions which get aborted
when one of these kinds of errors occurs, if it were the error would
have been reported 3 times, once for each loop iteration (that was
in "normal" bash mode, ie: the posix option is not on).
kre
