> That message is a reflection of where things currently are. It contains a
> patch that will allow bash-completion to work unchanged. (In a nutshell,
> bash-completion makes assumptions about what compgen will do with quoted
> null arguments that changed between bash-4.2 and bash-4.3.)
>
> I th
Chet Ramey writes:
> On 3/20/14 12:41 AM, Richard Tollerton wrote:
>>
>> I suppose that this change in behavior makes array variables more
>> consistent with normal variables, but I couldn't find anything in
>> CHANGES which obviously relates to this, so I'm not sure if this is a
>> bug or not.
On 3/18/14 9:59 AM, Stephane Chazelas wrote:
> With bash-4.3 as found on Debian's 4.3-2 package:
>
> $ bash -cO extglob 'echo *(.)'
> . ..
> $ bash -cO extglob 'echo *(foo)*'
> . .. a
> $ bash -cO extglob 'echo @(|foo)*'
> . .. a
>
>
> It looks like the regression was introduced by 4.3, as 4.2 d
On 3/20/14 12:41 AM, Richard Tollerton wrote:
>
> Old behavior, bash 4.2.45:
>
> $ bash -c 'set -u; echo ${#arr1[@]}'; \
> bash -c 'set -u; declare var1; echo ${#var1}'; \
> bash -c 'set -u; declare -a arr2; echo ${#arr2[@]}'
> bash: arr1: unbound variable
> bash: var1: unbound variable
> 0
>
>
