Description of problem: Suppose you have a file called ":1" (touch :1) Then the command "rm :<tab>" completes to "rm :\:" which is wrong because :1 contains only one colon (not two). Version-Release number of selected component (if applicable): bash-4.2.10-4.fc16.x86_64 How reproducible: always Steps to Reproduce: 1.See description 2. 3. Actual results: See description Expected results: Completion to "rm :1" or at least to "rm \:1" Additional info: 1. The F16 behaviour differs from the F15 behaviour. 2. I think it nothing to do with the fact that the bash command ":" does nothing.
Not a bug. bash's readline have special variable COMP_WORDBREAKS. `:' is considered as word separator.
echo $COMP_WORDBREAKS "'><=;|&(: unset COMP_WORDBREAKS echo $COMP_WORDBREAKS Now ':' is no more a separator! But still: 'rm :<TAB>' completes to 'rm :\:' I think, the bug should be reopened!
(In reply to comment #2) > echo $COMP_WORDBREAKS > "'><=;|&(: > unset COMP_WORDBREAKS > COMP_WORDBREAKS loses special meaning when unset, see man page > > echo $COMP_WORDBREAKS > > Now ':' is no more a separator! > > But still: > > 'rm :<TAB>' completes to 'rm :\:' > > I think, the bug should be reopened! Use something like COMP_WORDBREAKS=${COMP_WORDBREAKS/:/}