Ah, got it sorted out.
Not a bug, of course (:
Bash, when not in posix mode, clears the '-e' flag in subshell environments.
On 10/3/19, John W wrote:
> I'm seeing some strange behavior w/regard to `set -e` when invoking a
> shell function through a `$(...)` construct.
>
> I can't tell if it's a
I'm seeing some strange behavior w/regard to `set -e` when invoking a
shell function through a `$(...)` construct.
I can't tell if it's a bug or not; the manpage doesn't really mention
$() specially with regard to `set -e`, that I have found.
I made a SO post with a bunch of details here:
https:/
Hi All,
Below are some issues I found with history substitution. I am duplicating
its behavior in a somewhat different use, and found issues with the
documentation and bugs as described.
Jim Monte
From: jim
To: bug-bash@gnu.org
Subject: Issues with history substitution and its documentation
2019-10-03 13:58:40 -0400, Chet Ramey:
> On 10/2/19 11:38 AM, Stephane Chazelas wrote:
>
> > BTW, what's the point of the check_dev_tty() function? It seems
> > it just attempts to open the tty (the controlling one or the one
> > open on stdin), closes it, but doesn't return anything about the
> >
On 10/2/19 11:38 AM, Stephane Chazelas wrote:
> BTW, what's the point of the check_dev_tty() function? It seems
> it just attempts to open the tty (the controlling one or the one
> open on stdin), closes it, but doesn't return anything about the
> success of failure in doing so.
It's to make up f
