Re: [Help-bash] Very slow command completion when the current directory is slow to access

[Roman Rakus]

On 07/19/2013 02:07 AM, Peng Yu wrote:
> > It's likely your .bashrc is sourcing /etc/bash_completion* which almost
> > certainly does a whole lot of checks (including the contents of the
> > current directory) before returning possible completions. Start a shell
> > with bash --norc --noprofile to see if this fixes the issue. If so, stop
>
> `bash --norc --noprofile` does improve the speed.
>
> /opt/local/share/mercurial/contrib/bash_completion
> /opt/local/share/bash-completion/bash_completion
> /opt/local/etc/profile.d/bash_completion.sh
> /opt/local/etc/bash_completion.d
> /private/etc/bash_completion.d
>
> I have the above files related with bash_completion
>
> But I don't source any of them in my .bashrc (my OS is Mac OS X 10.8.4
> with macports). How to figure where bash_completion is sourced? (But
> then it may be in a system file, I'd rather not to change any system
> file. Is there a way to disable bash_completion?)
You can get what completions you have defined:
complete -p

But even bash native tab completion could be slow just because it scans 
directory and it can be current working directory.

Are you talking about filename tab-completion or executable file 
tab-completion?

RR