Restricted tab-completion is annoying

Aaron C. de Bruyn ubuntu-devel-discuss at
Thu Oct 11 05:01:02 UTC 2007

Ok--I'm sorry, but none of what you said made any sense to me.

> I don't see the point why filenames needs to be tab-completed on default, it
> does it when it's necessary.

I'm asking why tab-completion changed from allowing tab-completion of EVERY file to being restricted.
It sounds like you are asking why it needs to be on at all.

My response to that is that it is a feature that people like and use.  It's been that way for as long as I can remember.  At least 8 years.

> Filenames does tab-complete on certain tasks and applications, depending on
> what are you trying to accomplish?

Is that a question or statement?

Yes, you hit tab to complete certain commands and filenames.  It seems like Ubuntu is trying to be helpful by showing you only the things it thinks you need.

> For example, certain applications that require an input needs to
> tab-complete a filename on it's parameters (i.e. rsync), and
> executable files like python, perl, ruby & bash scripts would need
> tab-completion to execute.

Yes, that is why there is tab completion--because there are so many Linux command that take filenames as parameters.

> If you really want to autocomplete your filenames, you might as well make
> your files executable,

So you are saying I should chmod +x all my videos, pictures, and music files in order to use tab-completion.  That's an even worse solution.  They aren't executable files.  They are data files that need to be interpreted BY programs that I execute.

> and lastly why do you think this is necessary?

Why do I think what is necessary?  Tab completion?  Disabling the new restrictions to tab-completion?  Being able to use a feature that has been in bash forever but was recently (in my opinion) crippled?


More information about the Ubuntu-devel-discuss mailing list