Opened 15 years ago
Closed 12 years ago
#23913 closed enhancement (wontfix)
allow selective enabling of bash-completion modules
Reported by: | jabronson@… | Owned by: | raimue (Rainer Müller) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: | bash-completion |
Description
Currently there is no way to selectively enable bash-completion modules; ". /opt/local/etc/bash_completion
" causes all 149 modules in /opt/local/etc/bash_completion.d
to be loaded and results in an unnecessary slowdown in shell startup time (e.g. 0.635s on my new Macbook Pro when the disk cache is cold (0.224s when hot)).
Other bash-completion distributions provide a facility for selectively enabling modules (e.g. eselect bashcomp enable ...
on Gentoo). Could MacPorts make use of their prior art somehow?
Change History (4)
comment:1 Changed 15 years ago by jmroot (Joshua Root)
Owner: | changed from macports-tickets@… to raimue@… |
---|---|
Port: | bash-completion added |
Version: | 1.8.2 |
comment:2 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Now that MacPorts has subports, the bash-completion port could be broken into subports that could be installed separately...
comment:3 Changed 12 years ago by raimue (Rainer Müller)
The original ticket description referred to Gentoo's eselect bashcomp
which makes a per-user configuration possible. The slow shell startup has been improved in the upcoming bash-completion 2.0, of which the current beta version is available for testing in the bash-completion-devel port.
comment:4 Changed 12 years ago by raimue (Rainer Müller)
Resolution: | → wontfix |
---|---|
Status: | new → closed |
bash-completion and bash-completion-devel are now both version 2.0 as of r95135. The shell startup is very fast now, so there should be no need for selective enabling of completions.
Please remember to fill in the Port field and cc the maintainer.