Loading /etc/bash_completion takes 3 seconds on my Alix-based system (which has an AMD Geode 500 MHz CPU).
Bash completions are loaded in a number of places including via /etc/profile. A non-invasive way to disable this is to add
BASH_COMPLETION=1
to the start of /etc/profile.
/etc/profile.d/bash_completion.sh will only load /etc/bash_completion if BASH_COMPLETION is the empty string.
If you get an error:
sed: can't read 1: No such file or directory
Then something else is still trying to load /etc/bash_completion. In my base, this was ~/.bashrc.
Loading /etc/bash_ completion takes 3 seconds on my Alix-based system (which has an AMD Geode 500 MHz CPU).
Bash completions are loaded in a number of places including via /etc/profile. A non-invasive way to disable this is to add
BASH_COMPLETION=1
to the start of /etc/profile.
/etc/profile. d/bash_ completion. sh will only load /etc/bash_ completion if BASH_COMPLETION is the empty string.
If you get an error:
sed: can't read 1: No such file or directory
Then something else is still trying to load /etc/bash_ completion. In my base, this was ~/.bashrc.