Mail Archives: cygwin/2005/10/15/23:47:12
Op Sat, 15 Oct 2005 15:11:53 -0600 schreef Eric Blake
in <43517099 DOT 5080908 AT byu DOT net>:
[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/
- Raw text -