-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Larry Hall on 7/31/2005 11:08 AM: > If you're saying that there's a 19 second delay to invoke bash with > bash_completion on (with you weak machine), that's more of a concern > than a 19 second delay in the setup installation process. If it is > the former, I think some care needs to be taken here. I myself run > Cygwin on a variety of hardware, from a 600Mhz P3 laptop to a dual > 2.4Ghz P4. If there's much more than a second or so slowdown in > starting bash with bash_completion on by default, we're going to see > lots of complaints on the list about the change. And if that is indeed > the case, my vote would be to install bash_completion and provide a > README and/or very simply configure script to enable it.
Sourcing bash_completion must be done for every interactive shell startup, login or otherwise, for the completions to be available. And even on my 2.5 GHz WinXP machine, "time . /etc/bash_completion" reports 1.346 s. Also, I anticipate the time will only grow as upstream adds more completions (it already includes 266 kbytes among 28 files to be sourced). So based on your argument, I've decided that the bash_completion is not enabled by default, and that you must edit your ~/.bashrc to source it (and make sure your ~/.bash_profile sources ~/.bashrc, to cover login shells) if you desire the features. I will also provide patches to base-files to make this more obvious to new users. - -- 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 iD8DBQFC7hXN84KuGfSFAYARAh8iAJ4w09AbdxqOwJcJAGt968OwzIU7HACfcAsh JJCLMjFVS1yaReA6v6PCh+w= =RE9h -----END PGP SIGNATURE-----
