I started with this problem:
The only difference was that in my case the command in question was
configure. I successfully applied the solution described in that question (i.e. you should remove the completion with
complete -r configure). The problem is... if you try the completion once, it comes back from the dead.
$ complete -p configure complete -F _configure configure # Hum... there *is* a completion $ complete -r configure # So let's remove it! $ complete -p configure bash: complete: configure: no completion specification # Ha! It's gone! # Let's try it now. $ ./configure <TAB> # Damn! It still doesn't work! $ complete -p configure # It's back from the dead!!! complete -F _configure configure
Does anybody know how to solve this?
One more piece of information:
complete -p configure to my
.bashrc and then it started giving me this error on startup:
bash: complete: configure: no completion specification
This is interesting. The completion for
configure doesn't exist at startup... It seems that some kind of dynamic completion definition is happening here.