Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'Reading man pages in the current directory' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Reading man pages in the current directory
Authored by: WillyT on Apr 04, '03 11:11:43PM

Sorry but this won't find most of my man pages. If I "unsetenv MANPATH" then run manpath I lose most of finks manpages and all of X11's manpages. I'll continue to keep MANPATH set.

I remember a while back that an OSX update unset my MANPATH and I'm wondering where the heck did all my manpages go.

[ Reply to This | # ]
Reading man pages in the current directory
Authored by: Anonymous on Apr 05, '03 05:31:07PM
The problem with relying on site-wide manpath's is that it is tailored to the system, not the user. A real everyday example would be software I write. I install the software in my home directory ($HOME/bin, $HOME/man, $HOME/etc, ...). I don't want everyone else on the system reading my manpages. In fact, I keep my home directory permissions set at 700. Does my software belong in /usr/local? Not if it's a utility that only I would use (software only a mother could love, trust me!). Not if it's still buggy. Not if I don't want others using it. Solution? A custom MANPATH (the standard UNIX way).

Really, I'm not trying to say the original suggestion of writing a script is wrong. In fact, it's a nice script - short and simple. The point I'm trying to make is that provisions were put in place to deal with non-sitewide man pages 20 years ago in UNIX. The script re-invents the wheel - and the old wheel is still better.


[ Reply to This | # ]