Re: Resolving quoted COMP_CWORD on bash-4

The patch seems to to work all right. I've tested nested strings and they all return the right CWORD with bash-4.0.33 patched: $ a foo'bar# Returns foo'bar $ a "foo'' bar # Returns "foo'' bar I just found a corner case bug, but that seems to be in bash-3 as well. The command: $

Re: Resolving quoted COMP_CWORD on bash-4

Freddy Vulto wrote: > I just found a corner case bug, but that seems to be in bash-3 as > well. The command: > >$ b' > > doesn't complete with commands but with local filenames, although this > is a valid command: > >$ b'ash' That will never work. It's fundamental readline behavior t

wait with trap SIGCHLD: different behaviour in 3.2 and 4.0

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

Re: wait with trap SIGCHLD: different behaviour in 3.2 and 4.0

power...@powerman.name wrote: > Bash Version: 4.0 > Patch Level: 28 > Release Status: release > > Description: > Looks like 'wait' command in bash-4 is broken: if used together > with 'trap myhandler SIGCHLD' the 'wait' (without params) exit > just after receiving first ch