read doesn't work with piped stdin

2007-11-18 Thread Blaine Simpson
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc -I/usr/src/packages/BUILD/bash-3.2 -L/usr/src/packages/BUILD/bash-3.2/../readline-5.2 Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MAC

"exit" doesn't work from inside of PIPED read block

2007-11-18 Thread Blaine Simpson
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc -I/usr/src/packages/BUILD/bash-3.2 -L/usr/src/packages/BUILD/bash-3.2/../readline-5.2 Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MAC

Re: interpretation of pound (#) character inside a bracket expression inside single quotes inside backticks

2007-11-18 Thread Chet Ramey
Poor Yorick wrote: > > Description: > The pound character (#), when located inside a bracket expression > inside > single quotes inside backticks, is incorrectly interpreted as the bash > comment token. Patch 1 to bash-3.2 fixed this. Chet -- ``The lyf so short, the c

interpretation of pound (#) character inside a bracket expression inside single quotes inside backticks

2007-11-18 Thread Poor Yorick
Configuration Information [Automatically generated, do not change]: Machine: i686 OS: linux-gnu Compiler: gcc -m32 Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='linu x-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/path /to/bash-3.2/share/loc