[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: PATCH: fixes to BASHOPT and -O optname behavior
From: |
Chet Ramey |
Subject: |
Re: PATCH: fixes to BASHOPT and -O optname behavior |
Date: |
Fri, 6 May 2016 11:31:19 -0400 |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.0 |
On 5/1/16 3:24 AM, Grisha Levit wrote:
> Please consider the patch below, which fixes the following:
>
> * When starting a shell with both $BASHOPTS in the environment and -O
> optname options, processing of environmental $BASHOPTS was blocked due to
> the variable already being present and readonly by this time.
> * When extdebug was toggled, it caused toggling only of functrace, not of
> both functrace and errtrace, as described in the docs
> * When extdebug was toggled, SHELLOPTS were not being updated to reflect
> the new err/functrace state
> * When the shell did not enable extdebug due to the debugger init file not
> being present, $BASHOPTS was not being updated to reflect this change.
Thanks for the fix. This will be in bash-4.4.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/