[9fans] Plan9 port man pages

[9fans] Plan9 port man pages

[Ishwar Rattan]

System is Linux Mandrake-9.1

Just adding /usr/local/plan9/man to MANPATH only works for
man page entries that are unique to plan9 but all others
have matches in linux man pages or ones that start with a digit
(9c etc.) man command treats it as a section #.

So, what os the correct way to handle it?

-ishwar

Re: [9fans] Plan9 port man pages

[Lyndon Nerenberg]

> Just adding /usr/local/plan9/man to MANPATH only works for
> man page entries that are unique to plan9 but all others
> have matches in linux man pages or ones that start with a digit
> (9c etc.) man command treats it as a section #.
>
> So, what os the correct way to handle it?

cat > $HOME/bin/9man << EOF
#!/bin/sh
exec man -M /usr/local/plan9/man $*
EOF

Re: [9fans] Plan9 port man pages

[William Josephson]

On Tue, May 18, 2004 at 08:54:23PM -0400, Ishwar Rattan wrote:
> Just adding /usr/local/plan9/man to MANPATH only works for
> man page entries that are unique to plan9 but all others
> have matches in linux man pages or ones that start with a digit
> (9c etc.) man command treats it as a section #.
>
> So, what os the correct way to handle it?

There's a script called 9man (or man9 if you want history
expansion to work) that looks up plan 9 man pages.  It also
adds some troff magic to make the pages render better, at
least under FreeBSD.  I haven't ported over the stuff I
added to my version of the Plan 9 port yet, but it brings
in lookman and friends, too.  Probably not worth the effort.

Re: [9fans] Plan9 port man pages

[Scott Schwartz]

| > So, what os the correct way to handle it?

I think man should return all matching pages by default
(the -a option.)  In linux you can set MANOPT=-a.