Restricted tab-completion is annoying

Fergal Daly fergal at
Fri Oct 12 13:49:15 UTC 2007

On 12/10/2007, Aurélien Naldi <aurelien.naldi at> wrote:
> > So anyone who disliked anything in the system bashrc 10 years should
> > have skipped all updates since?
> >
> > Why do I have to opt out of bug future fixes and improvements just
> > because somebody else prefers their way of tab-completion?
> I have to disagree here.
> bash has tons of configuration files:
>   /etc/bash.bashrc
>   /etc/skel/.bashrc
>   your own .bashrc
> you can put changes in any of these files, but obviously if you choose
> to modify one of the /etc file, you will have to deal with it! Just
> like you do for every other configuration file!
> dpkg deals with config files changes pretty well I think, you can rely
> on it to be warned when there is a new version and then merge your
> changes in it.
> you can also follow the vim way: add "source /etc/bash.basrc.local" at
> the end of your bash.bashrc file and put whatever big changes you want
> in this other file.
> Then you have the big changes you want and you can painlessly merge
> them with any new version.
> I have to agree with the previous comment: can we stop this madness now ?
> Config file conflicts are IMHO nicely handled in dpkg, just use it...

Unlike the original poster, I'm not advocating changing the system
files (although that would probably work reasonably well for me). As
plain old user, I can

A /etc/bash_completion
B I can hack up my own version
C I can just abandon smart completion entirely

B is the situation I described above and both A nor B make life worse
than before.

When different people prefer different things (and the things really
are different and mutually incompatible), it is not unreasonable to
expect to a way to indicate your preference. Especially when something
was the status quo for such a long time.

I don't really feel strongly about this particular feature but I do
get annoyed when people make incompatible changes to UIs without
giving an easy route to the old UI. It's OK if the new way is a better
way to access the same functionality but in this case it's not. There
are plenty of other examples - Firefox 2.0's tabs, Evolution 2.10's
quick search (which made part of the search criteria invisible),


> --
> Aurélien Naldi
> --
> Ubuntu-devel-discuss mailing list
> Ubuntu-devel-discuss at
> Modify settings or unsubscribe at:

More information about the Ubuntu-devel-discuss mailing list