From: cyg Simple <cygsimple@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: regex man-page confusion
Date: Wed, 19 Sep 2018 11:50:00 -0000 [thread overview]
Message-ID: <86910f1f-6d8f-d61b-6b82-eacdb25fe7f5@gmail.com> (raw)
In-Reply-To: <bd54fcce-44d4-fa81-f1d6-cd5452ead488@towo.net>
On 9/19/2018 3:12 AM, Thomas Wolff wrote:
> Am 17.09.2018 um 14:49 schrieb cyg Simple:
>> On 9/16/2018 5:52 PM, Thomas Wolff wrote:
>>> Thanks; on the system with both packages not installed, man -w regcomp
>>> says nothing (rather than "No manual entry...");
>>> `manpath` reveals /usr/share/man:/cygdrive/c/Windows/SUA/usr/share/man
>>> and in fact, the man page displayed comes from my SUA installation. But
>>> $MANPATH is empty, so what makes cygwin `man` access the SUA man
>>> pages???
>>>
>> As per [1] you need to check your /etc/man_db.conf file.
> I hadn't mentioned that but I had checked it, grep -i sua only found
> "usually".
>
> Found the culprit meanwhile: /cygdrive/c/Windows/SUA/usr/lib was in my
> PATH. If I remove it, the SUA man page is not displayed anymore.
> So the more specific question: What makes cygwin 'man' check the PATH
> (not the LD_LIBRARY_PATH) to find which library and - still - why does
> that lead it to SUA man pages???
Maybe in the mandb? Or maybe a ~/.manpath file? Or maybe an alias
with -M, --manpath specified? Or a SYSTEM environment variable
specified? It's complex and something cached the discovered manuals on
PATH. Maybe use of -W and -w can help you determine.
--
cyg Simple
prev parent reply other threads:[~2018-09-19 11:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-16 17:59 Thomas Wolff
2018-09-16 18:13 ` Marco Atzeri
2018-09-16 21:57 ` Thomas Wolff
2018-09-17 12:49 ` cyg Simple
2018-09-19 7:12 ` Thomas Wolff
2018-09-19 11:50 ` cyg Simple [this message]
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=86910f1f-6d8f-d61b-6b82-eacdb25fe7f5@gmail.com \
--to=cygsimple@gmail.com \
--cc=cygwin-apps@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).