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 t
-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. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Christopher Faylor on 7/29/2005 8:41 AM:
> On Fri, Jul 29, 2005 at 03:45:57PM +0200, Reini Urban wrote:
>
>>I've updated bash_completion last week, but did not do so with the
>>debugger, because I wanted to wait until your bash-3.0 will s
On Fri, Jul 29, 2005 at 03:45:57PM +0200, Reini Urban wrote:
>I've updated bash_completion last week, but did not do so with the
>debugger, because I wanted to wait until your bash-3.0 will stabilize.
>It's just at my private setup site, since it's no official package.
> http://tu.xarch.at/publ/cy
I've updated bash_completion last week, but did not do so with the
debugger, because I wanted to wait until your bash-3.0 will stabilize.
It's just at my private setup site, since it's no official package.
http://tu.xarch.at/publ/cygwin
Unfortunately my site died yesterday due to a hacker who tu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A long time ago, Reini proposed an ITP for bashdb and bash_completion:
http://cygwin.com/ml/cygwin-apps/2004-10/msg00423.html. Following through
that thread, the biggest controversy was bashdb, since it didn't play well
with bash-2.05b, and Reini didn
