Brendan Desmond writes:
> This does work=E2=80=94thank you. The cost, obviously, is that I can no lon=
> ger access the manpages of my host system in the same manner via the plumbe=
> r. Perhaps this would be a good exercises in hacking up a workaround so I c=
> an have the best of both worlds. I appreciate the tip.
In the default setup you get the manpage that corresponds to the
binary that would run from the command line. I.e. UNIX man(1)
searches based on $PATH, and plan9 man searches just plan9 manpages.
So, running /usr/bin/man will defer to the UNIX manpage over the
plan9 one; you'll only see the plan9 page if there's no corresponding
This is the behaviour you want. It ensures the documentation matches
the actual binary you'll be running. Since you know how your $PATH
is set up you will know which manpage to expect. If you only want
the plan9 or UNIX page, you need to explicitly run man prefixed by
'9' or 'u' respectively. E.g., to get the plan9 ls(1), you need
to run '9 man ls' in a normal MacOS setup.
You could also try changing the plumber to invoke 'u man -a' instead
of bare 'man'. In theory this will print both the UNIX and plan9
pages, but I haven't tested it. It might give you more than you
asked for, though.