gA: declare and assign vs. declare then assign

Configuration Information [Automatically generated, do not change]: Machine: i686 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash

Re: gA: declare and assign vs. declare then assign

On 1/15/14, 10:04 PM, Carlos Pita wrote: > Bash Version: 4.2 > Patch Level: 45 > Release Status: release > > Description: > > When declaring a global associative array inside a function and > assigning a value to it at the same time, then the array is not > globally visible. This doesn't h

history writing bug

Configuration Information [Automatically generated, do not change]: Machine: i686 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash

DEL character treated specially when preceded by a backslash when used in the RHS of the regex operator ([[ $'\177' =~ $'\\\177' ]])

The DEL ($'\177') character does not behave like the other control characters when used with the regex operator inside the test keyword. This example shows the difference in operation: ubuntu@ubuntu:~$ for c in $'\001' $'\a' $'\177' $'\377'; do for r in "$c" "\\$c" "\\[$c]"; do [[ $c =~ $r ]];

Re: Including \t, \T or \A at beginning of PS1 causes line wrap issues

+Cc: bug-bash Please do not take discussions off-list, it decreases the value of conversations for future readers. On 2014-01-16 23:13:35 -0600, David C. Rankin wrote: > A sanitized version w/o color. That detail matters -- please include the full scope of the issue in future when reporting issu