It's worth noting that the bash completion scripts are being started
twice when logging in either via a tty or bash's (-l) option. The fault
with that is that most systems are checking the shell in
/etc/profile.d/bash_completion.sh to see if its bash and then proceeding
to call the bash_completion itself, neglecting the fact that bash calls
/etc/bash.bashrc anyway which will do the same thing. Lucky for me i
rarely log in via tty, im usually in xterm and dont use the (-l) option,
but even with one go, those scripts that are being executed are
installed into /etc/bash_completion.d/ by the various packages that
feature specialized completion. Though we can't blame them because this
is exactly what was intended in the first place. The tag is passed back
to bash to address startup script execution times in order to speed up
this it is going to have to consider the existing scripts out there
already. For now maybe there is some way to cache this in a way that
would be efficient for both resources and users?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790043

Title:
  Bash-completion slows up the start of bash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/790043/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to