Re: Bash crashes on tab completion after unset COMP_WORDBREAKS

[Chet Ramey]

D.J. Capelis wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: x86_64-pc-linux-gnu-gcc
> Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
> -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash'
> -DSHELL -DHAVE_CONFIG_H   -I.  -I. -I./include -I./lib   -O2
> -march=native -pipe -fstack-protector
> uname output: Linux aes 2.6.26-DJC-AES #1 SMP Thu Jul 17 22:09:37 PDT
> 2008 x86_64 Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz GenuineIntel GNU/Linux
> Machine Type: x86_64-pc-linux-gnu
> 
> Bash Version: 3.2
> Patch Level: 33
> Release Status: release
> 
> Description:
> It seems like once COMP_WORDBREAKS is unset, the actually completion
> mechanism of bash gets very unhappy.  Presumably maybe it shouldn't work
> very well after this is unset, but it's probably best if it doesn't
> crash outright.

Yes, it's probably better that it not crash. :-)

It's also probably better that unsetting COMP_WORDBREAKS restores the
default set of word break characters while honoring the setting of
`hostcomplete' rather than having no word breaks at all.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer

Chet Ramey, ITS, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/