Change in bash tab completion behaviour

Daryl F wyatt at
Sat Apr 20 14:14:39 UTC 2013

On Sat, 20 Apr 2013, Phil Thomson wrote:

> Suppose I have a directory '/foo/'.
> If I type 'cd /foo[TAB]', it correctly completes to 'cd /foo/'.
> If I type 'ls /foo[TAB]', it completes to 'ls /foo ' with a space after it.
> This is different from before; I am used to all commands behaving the
> first way. I prefer this way because if there is a subdirectory, it is
> easy to switch to it. The second way has it so that I have to backspace
> and add the trailing slash manually before I can start typing the name
> of the subdirectory.
> This is something that has started happening recently with bash
> completion. Does anyone know what's going on?

I cannot reproduce this. Mine never add as the space on an ls command. I 
even tried removing the bash-completion port and still experienced it.

Do you have a an alias defined for ls that might be interfering with
(confusing) bash completion?


More information about the CRUX mailing list