Re: bash 4.4 and BASHOPTS containing extdebug in env

2016-04-27 Thread Chet Ramey
On 4/26/16 10:49 PM, Grisha Levit wrote: > Thanks for the explanation. I'd read that thread but thought the change > was supposed to only modify the behavior when explicitly specifying the > --debugger option. That also seems to be the gist of the original RedHat > bugzilla request that prompted

Re: bash 4.4 and BASHOPTS containing extdebug in env

2016-04-26 Thread Grisha Levit
Thanks for the explanation. I'd read that thread but thought the change was supposed to only modify the behavior when explicitly specifying the --debugger option. That also seems to be the gist of the original RedHat bugzilla request that prompted the thread: https://bugzilla.redhat.com/show_bug.

Re: bash 4.4 and BASHOPTS containing extdebug in env

2016-04-26 Thread Chet Ramey
On 4/25/16 10:45 PM, Grisha Levit wrote: > This seems new for 4.4. Having extdebug in BASHOPTS seems to change the > invocation behavior to mimic that of having specified the --debugger > option, which I don't think is usually the intention: It's always been the case. The --debugger option and -

bash 4.4 and BASHOPTS containing extdebug in env

2016-04-25 Thread Grisha Levit
This seems new for 4.4. Having extdebug in BASHOPTS seems to change the invocation behavior to mimic that of having specified the --debugger option, which I don't think is usually the intention: $ shopt -s extdebug; export BASHOPTS $ bash -c 'echo $BASH_VERSION; shopt -p extdebug' 4.3.42(1)-relea