From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26043 invoked by alias); 15 Oct 2005 21:11:59 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 26032 invoked by uid 22791); 15 Oct 2005 21:11:57 -0000 Received: from sccrmhc14.comcast.net (HELO sccrmhc14.comcast.net) (63.240.76.49) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Sat, 15 Oct 2005 21:11:57 +0000 Received: from [192.168.0.100] (c-67-172-242-110.hsd1.ut.comcast.net[67.172.242.110]) by comcast.net (sccrmhc14) with ESMTP id <2005101521115401400n4fvbe>; Sat, 15 Oct 2005 21:11:55 +0000 Message-ID: <43517099.5080908@byu.net> Date: Sat, 15 Oct 2005 21:11:00 -0000 From: Eric Blake User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) MIME-Version: 1.0 To: cygwin mailing-list Subject: Re: Where is documentation on bash "wait"? References: <101520051745.25630.43514022000160940000641E22007614380A050E040D0C079D0A@comcast.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2005-10/txt/msg00452.txt.bz2 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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 ebb9@byu.net 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 iD8DBQFDUXCZ84KuGfSFAYARAihEAJ9WEMJVS+MG74XExh+BS6fTAdI5xgCbB2QA DE+hMj+DSE7yXs4Z/dqhrK0= =d6U6 -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/