So to be clear, the changes I'm suggesting are:
* /etc/skel/.bashrc (pkg=base-files) change the progcomp check to an
un-commented
# enable programmable completion
[[ -e /etc/profile.d/bash_completion.sh ]] .
/etc/profile.d/bash_completion.sh
* /etc/bash.bashrc (pkg=bash): remove the progcomp
crap, wrong bug, meant to post that last on bug 1173728
--
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
@Peter: I am most probably misreading your comment about lack of
background execution support in shell scripts. Why can't we load the
completions with . /etc/bash_completion instead of .
/etc/bash_completion?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
/etc/profile.d/bash_completion.sh only sources /usr/share/bash-
completion/bash_completion if it hasn't been already. note the check on
-z $BASH_COMPLETION_COMPAT_DIR, which the giant bash_completion script
defines with
: ${BASH_COMPLETION_COMPAT_DIR:=/etc/bash_completion.d}
readonly
@Atanas: interesting idea to have bash load completions in the
background, but shell scripting as a language has NO support for doing
anything like this. You can't just have it happen in another thread,
because you need it to modify the context of the CURRENT shell.
You'd need a new major
bug 1173728 is about programmable completion being loaded by default, or
not. Further discussion about how and whether it is should go there.
Sorry for the tangent about it in this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The shell builtin command return can be used to exit early from a file
sourced with . or source.
bash_completion could protect itself from being re-sourced by doing
type __reassemble_comp_words_by_ref 2/dev/null return
Or maybe
complete -p paste 2/dev/null return
So complete -r; source
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
Hi Bryce,
I should start by saying the execution time of bash-completion depends a
lot of the amount of software installed in any particular computer. I
posted the this bug based on my experience with a laptop which I no
longer have. While the machine was older its specs weren't very bad --
AMD
Hi Atanas, thanks this is a good suggestion. Do you have a test case
handy for measuring the startup time?
** Changed in: bash-completion (Ubuntu)
Importance: Undecided = High
** Changed in: bash-completion (Ubuntu)
Status: New = Triaged
--
You received this bug notification because
--
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
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
11 matches
Mail list logo
