This is the mail archive of the cygwin-apps mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: whatever happened with bash_completion, bashdb


-----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 stabilize.
>>It's just at my private setup site, since it's no official package.
>> http://tu.xarch.at/publ/cygwin
> 
> 
> Just wanted to say that I'm very interested in getting these into the
> cygwin distribution myself.  They sound like very useful things to have.

In regards to bashdb, I've downloaded it, and started playing with it.  It
worked almost out-of-the-box with bash-3.0-10 (the only change was that
the configure script had to be told to look for /usr/bin/bash.exe, since
"strings /usr/bin/bash" fails).  Expect an upload request soon once I get
the g-b-s fitted for installing it correctly.

In regards to bash completion, I can either install it so that it gets
turned on by default when you select it in setup.exe (using
/etc/profile.d), or we can patch base-files'
/etc/defaults/etc/skel/.bashrc to tell the user how to turn it on.

The argument for on by default is that by using setup.exe to download
bash_completion, the user already knows they want it.  Well, that is
unless they download everything, just to have everything available.

The argument against on by default is that installing completions takes
time; 19 seconds on my Win98 266 MHz machine.  While it is not noticeable
on modern machines, it can be quite a startup penalty to pay for starting
bash on older machines if it is done by default (the penalty is only to
interactive shells; shell scripts do not suffer).  But disabling by
default means that using setup.exe is not enough, the user also has to
edit their .bashrc to turn it on.

I'm leaning towards turning it on by default, but welcome any opinions to
which approach is better.  Alas, bash_completion doesn't have a configure
script or Makefile (it is just a collection of shell source files), so it
will be a bit more work for me to get the g-b-s adjusted to it.

- --
Life is short - so eat dessert first!

Eric Blake             ebb9@byu.net
-----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

iD8DBQFC63wV84KuGfSFAYARAnvYAKDOWRim6dARdLayLe5iDDBJkJY23ACgijYs
OeIm9JsG59FQP9mfKed9mqc=
=kGWY
-----END PGP SIGNATURE-----


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]