-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to John Morrison on 8/4/2005 6:52 AM: > > I wouldn't have thought there would be much/any speed gained doing it this > way...?
There's no speed difference, whether bash_completion is sourced by /etc/profile.d/completion.sh or by ~/.bashrc. The difference is that sourced by ~/.bashrc, the user explicitly turned it on, so they are aware that they caused the delay; plus multiple users sharing a machine can independently decide whether or not they want to take the delay. But with /etc/profile.d, the user has no choice; bash_completion WILL be sourced, and cause the delay. I'm afraid there are too many people who blindly install every package without realizing the implications, but I'm willing for the next release of bash-completion to use /etc/profile.d if there are enough complaints of why the user has to edit ~/.bashrc in addition to installing bash-completion. (I guess if I ever do add an /etc/profild.d hook, I'd have to make sure bash_completion is idempotent, so that sourcing it the second time is a no-op, rather than doubling the delay of users that already edited their ~/.bashrc.) > > If somebody installs bash_completion then they shouldn't have a problem > with something taking longer, if they do, they should uninstall it > (removing the /etc/profile.d/ file) :) Removing the /etc/profile.d file is a partial solution, but then cygcheck would report the bash-completion package is incomplete. - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC8hNJ84KuGfSFAYARAm1aAKCiQ9u+a1+frnLoVd4o2DdkTTLJzACgvCq7 Vsb+Si172JT7hLhJOxM0Ask= =sJVb -----END PGP SIGNATURE-----
