Broken parsing of quoted strings in backquotes

Configuration Information [Automatically generated, do not change]: Machine: sparc OS: solaris2.7 Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='sparc' -DCONF_OSTYPE='solaris2.7' -DCONF_MACHTYPE='sparc-sun-solaris2.7' -DCONF_VENDOR='sun' -DLOCALEDIR='/usr/local/depot/bash-3.

Follow up to previous report

Configuration Information [Automatically generated, do not change]: Machine: sparc OS: solaris2.7 Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='sparc' -DCONF_OSTYPE='solaris2.7' -DCONF_MACHTYPE='sparc-sun-solaris2.7' -DCONF_VENDOR='sun' -DLOCALEDIR='/usr/local/depot/bash-3.

Re: Broken parsing of quoted strings in backquotes

> Machine Type: sparc-sun-solaris2.7 > > Bash Version: 3.2 > Patch Level: 0 > Release Status: release > > Description: > Parsing of quoted strings broken when string contains "# " sequence Apply the patches to bash-3.2. Patch 1 fixed this problem. Chet -- ``The lyf so short, the craft

Re: extglob breaks when it's inside a bash function

> Machine Type: i486-pc-linux-gnu > > Bash Version: 3.2 > Patch Level: 13 > Release Status: release > > Description: > > when using extglob inside a bash subshell it breaks, > I tested it with several members in #bash and they have the same problem This is not a bug. Enabling the `extglob' cha

Re: "bashbug" script

> Here was an interesting bug which was some what unexpected. > > cat <(find ./ -iname t{1,2,3}) > > this is a valid command according to bash due to a bugged expansion of > {1,2,3} and the process expansion. It becomes three commands: > > find ./ -iname t1 > find ./ -iname t2 > find ./ -iname