Nick Withers wrote:
> Unfortunately (or at least as I understand it), the contents of
> "/etc/manpath.config" don't matter if you have the "MANPATH"
> environment variable set. Did you happen to set this yourself
> (i.e., explicitly)?


    2006-07-13 13:09:50 [EMAIL PROTECTED] ~
    $ grep MANPATH .*
    .bash_history:echo $MANPATH
    .bash_profile:    MANPATH=$MANPATH:$HOME/cvs/man
    .bash_profile:    MANPATH=$MANPATH:$HOME/man
    .bash_profile:    MANPATH=$MANPATH:$HOME/share/man
    .bash_profile:export MANPATH=:$HOME/local/man

    2006-07-13 13:09:58 [EMAIL PROTECTED] ~
    $ echo $MANPATH

I use the same .bash_profile and .bashrc everywhere, with conditionals
for various platforms and configurations.  Tightening up the
conditionals, logging out, and logging in again:

    2006-07-13 13:12:55 [EMAIL PROTECTED] ~
    $ echo $MANPATH

    2006-07-13 13:12:56 [EMAIL PROTECTED] ~
    $ manpath

    2006-07-13 13:12:59 [EMAIL PROTECTED] ~
    $ man man


Micah wrote:
> That's where comes in handy

Yes, that's useful.

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.

Thanks everyone for your help.  :-)


_______________________________________________ mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to