From: Michael Wild <themiwi@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Does /etc/profile need to set MANPATH?
Date: Sat, 17 May 2014 20:59:00 -0000 [thread overview]
Message-ID: <5377A7CD.7010209@gmail.com> (raw)
In-Reply-To: <20140515133939.GQ2436@calimero.vinschen.de>
On 15.05.2014 15:39, Corinna Vinschen wrote:
[...]
>
> You still have to be able to handle MANPATH. Unfortunately the man page
> of man-db is a little tight-lipped on how MANPATH is handled exactly,
> other than that "its value is used as the path to search for manual
> pages."
>
> Whatever man does with MANPATH, it doesn't drop the default man paths,
> apparently.
>
> [...time passes...]
>
> Hmm. Interesting enough, the current /etc/man.conf already contains
> /usr/ssl/man. How long is it doing that already? If I had known that,
> I'd removed the /etc/profile.d/openssl.* files long ago :|
>
>
> Corinna
>
Dear all
AFAIK the behavior is as usual for *NIX search paths, with two notable exceptions:
* A trailing or leading colon means that at this position the default search path from the configuration files is inserted
* A double-colon (::) anywhere means that at this position the default search path is inserted
Refer to the ENVIRONMENT section of manpath(1), http://manpages.ubuntu.com/man1/manpath.1.
Cheers, and a pleasant weekend
Michael
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-05-17 18:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 18:57 Chris J. Breisch
2014-05-13 19:25 ` Corinna Vinschen
2014-05-14 17:08 ` Achim Gratz
2014-05-15 7:56 ` Corinna Vinschen
2014-05-15 13:18 ` Chris J. Breisch
2014-05-15 13:39 ` Chris J. Breisch
2014-05-15 13:49 ` Corinna Vinschen
2014-05-15 17:48 ` Larry Hall (Cygwin)
2014-05-16 12:14 ` Corinna Vinschen
2014-05-17 8:50 ` Achim Gratz
2015-07-20 12:09 ` Mikhail Usenko
2015-07-20 12:20 ` Michael DePaulo
2015-07-20 13:43 ` Mikhail Usenko
2015-07-20 14:15 ` Mikhail Usenko
2015-07-20 16:21 ` Achim Gratz
2014-05-16 20:00 ` Chris J. Breisch
2014-05-17 20:59 ` Michael Wild [this message]
2014-05-19 9:38 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5377A7CD.7010209@gmail.com \
--to=themiwi@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).