On 4/25/16 3:48 PM, Grisha Levit wrote:
> There seems to be a bug that if an array variable with a name matching one
> of the special single-character variables exists, then that variable is
> used during substring expansion and parameter transformation.
>
> There is also a potential issue with na
On 4/27/16 2:45 AM, Grisha Levit wrote:
> Any of the following will crash bash:
>
> declare -n ref=a[*]; ref=
> declare -n ref=a[@]; ref=
> declare -n ref=a[-1]; a=(); ref=
>
> declare -A A; declare -n ref='A[$unset]'; ref=
>
> They all produce "bad array subscript" errors so could be caught.
T
On 4/26/16 3:03 PM, Grisha Levit wrote:
> This behavior seems very strange. This example is with $@ but it seems the
> same for ${array[@]}
>
> The manual says for ${parameter:-word}:
>
>> If parameter is unset or null, the expansion of word is substituted.
>
> In this case, $@ is expanded as i
On 5/1/16 2:10 PM, Eric Pruitt wrote:
> On Sun, May 01, 2016 at 03:54:16AM -0400, Grisha Levit wrote:
>> Does the issue go away if you do a "bind 'set colored-stats off"' ?
>
> No. That already defaults to "off", and I don't override it. I ran the
> "bind" command anyway, and it didn't make a diff
On Sun, May 01, 2016 at 03:54:16AM -0400, Grisha Levit wrote:
> Does the issue go away if you do a "bind 'set colored-stats off"' ?
No. That already defaults to "off", and I don't override it. I ran the
"bind" command anyway, and it didn't make a difference.
Eric
Does the issue go away if you do a "bind 'set colored-stats off"' ?
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
