Where is documentation on bash "wait"?
Sat Oct 15 21:11:00 GMT 2005
-----BEGIN PGP SIGNED MESSAGE-----
According to Bas van Gompel on 10/15/2005 2:46 PM:
> Did /you/ try it?
Yes, as bash maintainer, I /did/ try it. However, I didn't realize that
there was a typo in the upstream bash_builtins.1 manpage; I just supposed
that the text that was there was all it needed - thanks for catching that,
and I will forward it upstream.
> It complains about not finding bash.1.
I haven't seen man complain - I wonder what your setup is that got a
complaint about the typo in the .so?
> Do you have a copy of bash.1 lying around somewhere?
cygwin man pages are purposefully compressed, so it should be bash.1.gz.
> To get this to work as I think it is intended, I need to:
> For some reason it doesn't work with a gzipped bash.1.
> (A bug in man? It looks like it doesn't gunzip in this case.)
Yes, man could be improved to follow .so that have alternate extensions
(so that .so man1/bash.1 follows man1/bash.1.gz) - you may want to report
that to the upstream man list.
Meanwhile, I've corrected my local copy of bash to work in spite of the
cygwin gzipping; the next bash release will have the slick trick of inline
referencing to the bash builtins section, thanks to your patch pointing
that out to me.
Life is short - so eat dessert first!
Eric Blake firstname.lastname@example.org
volunteer cygwin bash maintainer
-----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
-----END PGP SIGNATURE-----
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
More information about the Cygwin