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 -O extdebug (which is the same as putting extdebug in BASHOPTS) all do the same thing and try to start the debugger. Bash-4.3 was silent when it couldn't open the debugger start file. Bash-4.4 warns the user when it tries to start the debugger and can't open the start file. This change went in back in November 2014 as the result of this discussion: http://lists.gnu.org/archive/html/bug-bash/2014-11/msg00137.html -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, ITS, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
