From: Thomas Wolff <towo@towo.net>
To: cygwin-apps@cygwin.com
Subject: Re: regex man-page confusion
Date: Sun, 16 Sep 2018 21:57:00 -0000 [thread overview]
Message-ID: <cccf06b9-56b8-e82a-30c1-911d9e57a5ad@towo.net> (raw)
In-Reply-To: <1d6c60a3-5217-01d8-b7ec-781a9e822d93@gmail.com>
Am 16.09.2018 um 20:13 schrieb Marco Atzeri:
> Am 16.09.2018 um 19:59 schrieb Thomas Wolff:
>> (Sending this to cygwin-apps as I suspect it to be an installation or
>> packaging issue...)
>
>> I observe a confusing discrepancy between Cygwin installations on two
>> systems, all with cygwin 2.11.1:
>> On one system (both cygwin32 and cygwin64), /usr/share/man has
>> man3/regex.3.gz and man3p/regcomp.3p,
>> both pages describe functions regcomp, regexec, regerror and regfree,
>> but in different format (from man3, it says BSD manual).
>> On the other system, none of them exists, nor any other
>> /usr/share/man/*/reg* (MANPATH not set). But `man regcomp` nonetheless
>> displays a manpage, with those 4 functions and additionally wcs_regcomp
>> and wcs_regexec.
>> Can anyone resolve this weirdness?
>> Thanks, Thomas
>
> regex.3.gz belongs to cygwin-doc package
>
> https://cygwin.com/cgi-bin2/package-cat.cgi?file=x86_64%2Fcygwin-doc%2Fcygwin-doc-2.11.1-1&grep=regex.3.gz
>
>
> regcomp.3p belongs man-pages-posix
>
> https://cygwin.com/cgi-bin2/package-cat.cgi?file=x86_64%2Fman-pages-posix%2Fman-pages-posix-2013-a-1&grep=regcomp.3p
>
>
> I assume one system has both packages and the other not.
>
> As I have not the second installed, for me
>
> $ man regcomp
> No manual entry for regcomp
>
> Regards
> Marco
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???
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
next prev parent reply other threads:[~2018-09-16 21:57 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 [this message]
2018-09-17 12:49 ` cyg Simple
2018-09-19 7:12 ` Thomas Wolff
2018-09-19 11:50 ` cyg Simple
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=cccf06b9-56b8-e82a-30c1-911d9e57a5ad@towo.net \
--to=towo@towo.net \
--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).