Try perldoc instead of man for help with Perl modules. It reads the POD
embedded in the modules and does the :: to / or \ translation for you.
For example:
perldoc File::Basename
Would give you the POD embedded in /lib/perl5/5.6.1/File/Basename.pm.
It's also a good way to: a) make sure you're getting the documentation
relevant to the module, and not some artifact man page from an old
module installation; b) perl searches its PERL5LIB path and gives you
the documentation for the first instance of the module it finds so you
get the documentation for the module instance that perl would also use
at run time hence you can tell if you're loading an older/newer version
of the module than you were expecting.
Cheers!
Ian
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf
Of Rafael Kitover
Sent: January 24, 2003 3:50 AM
To: [EMAIL PROTECTED]
Subject: PROPOSAL: translate '::' to '.' in arguments to the man command
I have noticed that some man pages, for example perl modules below the
root namespace, are installed as Foo.Bar instead of Foo::Bar because
apparently windows file names cannot contain "::". Eg.
$ touch 'Foo::Bar'
touch: creating `Foo::Bar': Invalid argument
This is sufficiently different from UNIX to trip most people up,
especially those working with Perl. Further, filenames with one colon do
work, e.g. Touch 'Foo:Bar'.
For this reason I propose changing the "man" command in Cygwin to take
the special case of "::" into account and convert it to a ".", iff the
file containing "::" does not exist (might be supported in the future.)
If this is considered a good idea I'll be happy to make the patch.
Cheers,
--
Rafael
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
