Re: A programmable completoin bug?

[Clark J. Wang]

On Mon, Dec 5, 2011 at 11:10, Chet Ramey <chet.ramey@case.edu> wrote:

>
> I still can't reproduce it on Mac OS X or RHEL 5.7:
>

It's weird. :) Any other settings can affect this? What can I do to debug
more?


>
> $ echo $BASH_VERSION
> 4.2.20(8)-release
> $ type -a compspec_foo
> compspec_foo is a function
> compspec_foo ()
> {
>    local cmd=$1 cur=$2 pre=$3;
>    if [[ $cur = :* ]]; then
>         COMPREPLY=(changed changed/IGNORE_ME);
>    fi
> }
> $ complete
> complete -F compspec_foo foo
> $ set -x
> $ COMP_WORDBREAKS=${COMP_WORDBREAKS%?}
> + COMP_WORDBREAKS='
> "'\''@><=;|&('
> $ echo $COMP_WORDBREAKS
> + echo '"'\''@><=;|&('
> "'@><=;|&(
> $ foo :this-is-a-+ local cmd=foo cur=:this-is-a- pre=foo
> + [[ :this-is-a- = :* ]]
> + COMPREPLY=(changed changed/IGNORE_ME)
> changed
> + foo changed
> bash: foo: command not found
> $ foo :this-is-a-long-word+ local cmd=foo cur=:this-is-a-long-word pre=foo
> + [[ :this-is-a-long-word = :* ]]
> + COMPREPLY=(changed changed/IGNORE_ME)
> changed
> + foo changed
> bash: foo: command not found
>
>
> I wonder if there's some difference in our environments that's the cause.
>
> Chet
>
> --
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
>                 ``Ars longa, vita brevis'' - Hippocrates
> Chet Ramey, ITS, CWRU    chet@case.edu
> http://cnswww.cns.cwru.edu/~chet/
>