Re: Where is documentation on bash wait?
Buzz writes: I was hoping for ``our'' man-maintainer, being much more knowledgeable about such issues, to be proactive... ...If (s)he isn't I'll look into finding the upstream ``man''-list. I will forward this issues to the upstream man maintainer. Ciao Volker -- 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/
Re: Where is documentation on bash wait?
Op Sat, 15 Oct 2005 22:01:26 -0600 schreef Eric Blake in [EMAIL PROTECTED]: : According to Buzz on 10/15/2005 9:46 PM: [(possibly stale) bash.1 about somewhere.] : Hmm, I do have /usr/local/man on my manpath, and it did indeed have : man1/bash.1, but I don't know if that affected things. I don't think so, as long bash_builins.1.gz didn't have the dirname in the .so. : I'm curious how that's gonna work. My ``man'', after i've edited : bash_builtins.1(.gz) to mention man1/bash.1.gz me, says: : : | man1/bash.1.gz:1: warning: can't find character with input code 6 : : It seems like man can cope with a .so that points to a .gz if that is the : only line, but has problems if the .so points to a .gz when embedded in : remaining text. That appears to be an accurate description of this issue. : I'm not familiar enough with man to know what is going on : here, but it does seem like a man issue. Indeed (same here). : Meanwhile, I can distribute : bash.1 instead of bash.1.gz since that is all that works with the current : version of man. That does WJFFM. Thanks a lot for your efforts. [...] L8r, Buzz. -- ) | | ---/ ---/ Yes, this | This message consists of true | I do not -- | | // really is | and false bits entirely.| mail for ) | | //a 72 by 4 +---+ any1 but -- \--| /--- /--- .sigfile. | |perl -pe s.u(z)\1.as.| me. 4^re -- 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/
Re: Where is documentation on bash wait?
Op Sun, 16 Oct 2005 12:11:00 +0200 schreef Dr. Volker Zell in [EMAIL PROTECTED]: : Buzz writes: : I was hoping for ``our'' man-maintainer, being much more knowledgeable : about such issues, to be proactive... : ...If (s)he isn't I'll look into finding the upstream ``man''-list. : I will forward this issues to the upstream man maintainer. Great, thank you very much. L8r, Buzz. -- ) | | ---/ ---/ Yes, this | This message consists of true | I do not -- | | // really is | and false bits entirely.| mail for ) | | //a 72 by 4 +---+ any1 but -- \--| /--- /--- .sigfile. | |perl -pe s.u(z)\1.as.| me. 4^re -- 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/
Re: Where is documentation on bash wait?
I tried info and man and could not find any information on wait. I want to (using bash) Did you try 'man wait'? That would have pointed you to 'man bash', where as a bash builtin, wait is properly documented. Also, 'info bash' will tell you about bash builtins, or you can try 'help wait' for a short synopsis. (1) How do I wait for multiple children and wake up when the first one dies? wait (2) Examine the status code of the dead child and possibly spawn a new one? I don't know of any way in POSIX to do this, but it is not really specific to cygwin, so you might try asking a more appropriate mailing list. -- Eric Blake volunteer cygwin bash maintainer -- 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/
Re: Where is documentation on bash wait?
Siegfried Heintze wrote: I tried info and man and could not find any information on wait. I want to (using bash) (1) How do I wait for multiple children and wake up when the first one dies? (2) Examine the status code of the dead child and possibly spawn a new one? Where is the documentation on wait? Wait's a builtin so the documentation is in the bash(1) man page. -- I like kids, but I don't think I could eat a whole one. -- 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/
Re: Where is documentation on bash wait?
Op Sat, 15 Oct 2005 17:45:06 + schreef Eric Blake in [EMAIL PROTECTED]: [What the...] : I tried info and man and could not find any information on wait. I want to : (using bash) : : Did you try 'man wait'? That would have pointed you to 'man bash', where Did /you/ try it? It complains about not finding bash.1. Do you have a copy of bash.1 lying around somewhere? To get this to work as I think it is intended, I need to: 1) gunzip /usr/share/man/man1/bash.1.gz and /usr/share/man/man1/bash_builtins.1.gz 2) patch /usr/share/man/man1/bash_builtins.1 like so: --- /usr/share/man/man1/bash_builtins.1~2005-10-15 21:27:52.0 +0200 +++ /usr/share/man/man1/bash_builtins.1 2005-10-15 21:44:33.77000 +0200 @@ -10,6 +10,6 @@ ulimit, umask, unalias, unset, wait \- bash built-in commands, see \fBbash\fR(1) .SH BASH BUILTIN COMMANDS .nr zZ 1 -.so bash.1 +.so man1/bash.1 .SH SEE ALSO bash(1), sh(1) 3) re-gzip /usr/share/man/man1/bash_builtins.1, but not bash.1 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.) [...] L8r, Buzz. -- ) | | ---/ ---/ Yes, this | This message consists of true | I do not -- | | // really is | and false bits entirely.| mail for ) | | //a 72 by 4 +---+ any1 but -- \--| /--- /--- .sigfile. | |perl -pe s.u(z)\1.as.| me. 4^re -- 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/
RE: Where is documentation on bash wait?
Perhaps the problem is specific to your configuration -- man wait does indeed point me to man bash, and the bash manpage does indeed cover wait (I searched for SHELL BUILTIN COMMANDS based on early text in the page, and then searched from the top of that section for wait -- worked like a charm. stephan(); -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bas van Gompel Sent: Saturday, October 15, 2005 1:46 PM To: cygwin@cygwin.com Subject: Re: Where is documentation on bash wait? Op Sat, 15 Oct 2005 17:45:06 + schreef Eric Blake in 101520051745.25630.4351402200016094641E22007614380A050E040D0C079D0A @comcast.net: [What the...] : I tried info and man and could not find any information on wait. I want to : (using bash) : : Did you try 'man wait'? That would have pointed you to 'man bash', where Did /you/ try it? It complains about not finding bash.1. Do you have a copy of bash.1 lying around somewhere? To get this to work as I think it is intended, I need to: 1) gunzip /usr/share/man/man1/bash.1.gz and /usr/share/man/man1/bash_builtins.1.gz 2) patch /usr/share/man/man1/bash_builtins.1 like so: --- /usr/share/man/man1/bash_builtins.1~2005-10-15 21:27:52.0 +0200 +++ /usr/share/man/man1/bash_builtins.1 2005-10-15 21:44:33.77000 +0200 @@ -10,6 +10,6 @@ ulimit, umask, unalias, unset, wait \- bash built-in commands, see \fBbash\fR(1) .SH BASH BUILTIN COMMANDS .nr zZ 1 -.so bash.1 +.so man1/bash.1 .SH SEE ALSO bash(1), sh(1) 3) re-gzip /usr/share/man/man1/bash_builtins.1, but not bash.1 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.) [...] L8r, Buzz. -- ) | | ---/ ---/ Yes, this | This message consists of true | I do not -- | | // really is | and false bits entirely.| mail for ) | | //a 72 by 4 +---+ any1 but -- \--| /--- /--- .sigfile. | |perl -pe s.u(z)\1.as.| me. 4^re -- 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/ -- 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/
Re: Where is documentation on bash wait?
-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 [EMAIL PROTECTED] 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/
Re: Where is documentation on bash wait?
Op Sat, 15 Oct 2005 15:11:53 -0600 schreef Eric Blake in [EMAIL PROTECTED]: [Ahhh] : : 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. Thank you for doing this. : 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? I'd think it's quite normal... (On several systems) I get: | standard input:14: can't open `bash.1': No such file or directory | BASH_BUILTINS(1) BASH_BUILTINS(1) | [...] : Do you have a copy of bash.1 lying around somewhere? : : cygwin man pages are purposefully compressed, so it should be bash.1.gz. I'm aware of that. I was WAGging you didn't get the error, having a (possibly stale) bash.1 about somewhere. : 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. That would be even better. I was just thinking about having: man1/bash.1.gz in the bash_builtins page (just like man1/wait.1 contains: ``.so man1/bash_builtins.1.gz'') I was hoping for ``our'' man-maintainer, being much more knowledgeable about such issues, to be proactive... ...If (s)he isn't I'll look into finding 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. I'm curious how that's gonna work. My ``man'', after i've edited bash_builtins.1(.gz) to mention man1/bash.1.gz me, says: | man1/bash.1.gz:1: warning: can't find character with input code 6 | man1/bash.1.gz:1: warning: can't find character with input code 3 | man1/bash.1.gz:1: warning: can't find character with input code 12 | man1/bash.1.gz:1: warning: can't find character with input code 127 | man1/bash.1.gz:1: warning [p 1, 2.3i]: cannot adjust line | man1/bash.1.gz:1: warning [p 1, 2.5i]: cannot adjust line | groff: troff: Signal 11 | grotty:standard input:163:warning: no final `x stop' command | BASH_BUILTINS(1) BASH_BUILTINS(1) | [...] L8r, Buzz. -- ) | | ---/ ---/ Yes, this | This message consists of true | I do not -- | | // really is | and false bits entirely.| mail for ) | | //a 72 by 4 +---+ any1 but -- \--| /--- /--- .sigfile. | |perl -pe s.u(z)\1.as.| me. 4^re -- 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/
Re: Where is documentation on bash wait?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Buzz on 10/15/2005 9:46 PM: : Do you have a copy of bash.1 lying around somewhere? : : cygwin man pages are purposefully compressed, so it should be bash.1.gz. I'm aware of that. I was WAGging you didn't get the error, having a (possibly stale) bash.1 about somewhere. Hmm, I do have /usr/local/man on my manpath, and it did indeed have man1/bash.1, but I don't know if that affected things. I'm curious how that's gonna work. My ``man'', after i've edited bash_builtins.1(.gz) to mention man1/bash.1.gz me, says: | man1/bash.1.gz:1: warning: can't find character with input code 6 It seems like man can cope with a .so that points to a .gz if that is the only line, but has problems if the .so points to a .gz when embedded in remaining text. I'm not familiar enough with man to know what is going on here, but it does seem like a man issue. Meanwhile, I can distribute bash.1 instead of bash.1.gz since that is all that works with the current version of man. - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -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 iD8DBQFDUdCW84KuGfSFAYARApvbAKDRDVPBqr1rkGCOreqJmYRnyXHnRwCgvIq9 n1NazcT+c9tdi+e2kjsttxw= =LRRL -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/
