Date: Thu, 13 Jul 2006 20:38:29 -0400 From: J <jsunx1@bellsouth.net> To: freebsd-questions@freebsd.org Subject: Re: 6.1-RELEASE-i386 man broken? Message-ID: <20060714003829.GA27743@brokedownpalace> In-Reply-To: <000f01c6a6ba$6d1d4340$0a10a8c0@holgerdanske.local> References: <20060714014823.c4d0b759.nick@nickwithers.com> <000f01c6a6ba$6d1d4340$0a10a8c0@holgerdanske.local>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2006-07-13 (Thu) 13:25:04 [+0000], David Christensen wrote: > Matthew Seaman wrote: > > Please read what I wrote more carefully. To summarize: don't set > > $MANPATH in your environment, and the man(1) command will work > > correctly. > > Now I understand: > > > The environment variable MANPATH should in general not be set, as > > that will override the effects of /etc/manpath.config. > I ran into and had to solve this problem myself when first coming to FreeBSD, recently, as my transported Linux bash configs contained MANPATH=$MANPATH:/custom/manpath. What I never figured out was the rationale for this. Anyone mind me asking what's wrong with MANPATH or why manpath.config is exclusively favored? For instance, while I have a /usr/lib/man.conf on my Linux system and can set the default manpath there, man happily coexists with any MANPATH. How does one add a custom manpath without root privileges? Etc. Just curious; thanks.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060714003829.GA27743>