From: Mikhail Usenko <cygwin@inbox.ru>
To: cygwin@cygwin.com
Subject: Re: Does /etc/profile need to set MANPATH?
Date: Mon, 20 Jul 2015 13:43:00 -0000 [thread overview]
Message-ID: <20150720164249.a52b6073a83c38241696802f@inbox.ru> (raw)
In-Reply-To: <CAMKht8hM=ua-chfZUtEYo9OaN20c6s6VU53d6hq1HYLoz+3XNA@mail.gmail.com>
On Mon, 20 Jul 2015 08:20:12 -0400
Michael DePaulo <...> wrote:
> On Mon, Jul 20, 2015 at 8:09 AM, Mikhail Usenko <cygwin@inbox.ru> wrote:
> > On Sat, 17 May 2014 10:37:30 +0200
> > Achim Gratz <...> wrote:
> >
> >> Corinna Vinschen writes:
> >> > Whatever, it looks like MANPATH can really go away. Achim, do your worst.
> >>
> >> Done.
> >>
> >
> > Besides defining MANPATH (and the other variables such as INFOPATH and PATH which can be modified by the user's .bash_profile) /etc/profile also did export the MANPATH variable.
> > Now it does not and I suppose that user's skeleton file /etc/skel/.bash_profile should provide user-defined MANPATH pro-forma as an exported environment variable or else it will have no effect.
> >
> > --
> > Mike
> [...]
>
> Why does Cygwin need to define MANPATH by default? Cygwin uses
> /etc/man_db.conf, just like the Red Hat family of Linux distros. (The
> Debian family uses /etc/manpath.config).
>
The point is that the current stanza for MANPATH in /etc/skel/.bash_profile
--- %< ---
# Set MANPATH so it includes users' private man if it exists
# if [ -d "${HOME}/man" ]; then
# MANPATH="${HOME}/man:${MANPATH}"
# fi
--- >8 ---
is not useful because for:
1) if you run manpath from the command line in clean Cygwin installation you find out that
"${HOME}/man" is (and always remains) in your searching path by default even if you have no "${HOME}/man"
in your home directory path
2) if you are minded to add your private man pages like this:
MANPATH="${HOME}/my-man-pages:${MANPATH}"
it will not work. Now you should mark the variable for export:
export MANPATH="${HOME}/my-man-pages:${MANPATH}"
I suggest to change the skeleton file to something like this:
--- %< ---
# Set MANPATH so it includes users' private man
# export MANPATH="${HOME}/manpages:${MANPATH}"
--- >8 ---
--
Mike
--
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:[~2015-07-20 13:43 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 [this message]
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
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=20150720164249.a52b6073a83c38241696802f@inbox.ru \
--to=cygwin@inbox.ru \
--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).