I agree that one should never source bash_completion from the wrong shell - it is a case of user error.
But I suspect it's a relatively common mistake to make (for example, Mandriva users expect the system shell to always be bash, and /etc/profile.d is used in that way). Also, adding shell defaults by dropping them into profile.d is the obvious (albeit, wrong) way to do it: it's the only directory into which packagers can add scripts. Indeed, reading /etc/bashrc explicitly says: # It's NOT good idea to change this file unless you know what you # are doing. Much better way is to create custom.sh shell script in # /etc/profile.d/ to make custom changes to environment. This will # prevent need for merging in future updates. So that's what I did - and it broke. The change I suggest, while technically unnecessary, should add some resilience against a particular way to really mess up a system. I think it's sufficiently non-invasive that it's worth doing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/565729 Title: bash-completion doesn't check shell is BASH -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
