From: Linda Walsh <cygwin@tlinx.org>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: man incredibly slow because it scans for share directory in PATH??
Date: Mon, 13 Jun 2016 19:38:00 -0000 [thread overview]
Message-ID: <575EF950.2010809@tlinx.org> (raw)
In-Reply-To: <87y46acvww.fsf@Rainer.invalid>
Achim Gratz wrote:
> Riedel,Till (TM) writes:
>> IMHO at least in Windows/Cygwin creating MANPATH from PATH makes no
>> sense! (although I now get the idea what was the rationell!)
>> Reasonably setting MANPATH should IMHO be a default...
>
> MANPATH is unset in a standard Cygwin installation since quite some time
> and it wasn't constructed from PATH before that change.
----
I.e. in a console window, if you type:
> echo $MANPATH
What do you see? On my system, I see a rather short version that
isn't exactly right as it has non-existing directories in it:
/usr/local/man:/usr/share/man:/usr/man::/usr/openwin/man
But since they are at the end, it doesn't much seem to matter. On
a linux distro, All of the directories in MAN seem to exist and have
man pages in them:
/home/lindaw/share/man:/usr/local/man:/usr/local/share/man:\
/usr/share/man:/opt/kde3/share/man:/usr/man:/opt/dx/man:\
/opt/mpich/man
(backslashes inserted by me for readability).
According to the cywin manpage for man, man has a config file
that tells it where to search in "/etc/man_db.conf".
--
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:[~2016-06-13 18:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 10:50 Riedel,Till (TM)
2016-06-12 14:41 ` Andrey Repin
2016-06-12 17:18 ` Riedel,Till (TM)
2016-06-12 17:22 ` Achim Gratz
2016-06-13 19:38 ` Linda Walsh [this message]
2016-06-14 7:45 ` Achim Gratz
2016-06-14 22:22 ` Linda Walsh
2016-06-15 4:58 ` Achim Gratz
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=575EF950.2010809@tlinx.org \
--to=cygwin@tlinx.org \
--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).