This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: whatever happened with bash_completion, bashdb
- From: "John Morrison" <john at morrison dot mine dot nu>
- To: cygwin-apps at cygwin dot com
- Date: Mon, 1 Aug 2005 13:46:00 +0100 (BST)
- Subject: Re: whatever happened with bash_completion, bashdb
- References: <42EA2BBD.60708@byu.net> <157.247.252.11.1122644757.wm@webmail.inode.at> <20050729144154.GI9031@trixie.casa.cgf.cx> <42EB7C16.7000901@byu.net> <6.2.1.2.0.20050731125822.03002ee0@pop.prospeed.net> <42EE15CD.1010803@byu.net>
- Reply-to: john at morrison dot mine dot nu
On Mon, August 1, 2005 1:30 pm, Eric Blake said:
> 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.
Not a problem, just send me the patches :)
J.