From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin-apps@cygwin.com
Subject: man-pages-linux needs case sensitive directories
Date: Wed, 15 Feb 2023 00:11:14 -0700 [thread overview]
Message-ID: <0e730b68-f661-ba13-9020-acce69932067@Shaw.ca> (raw)
Hi folks,
Linux man pages 6.03 has been released.
I realized that some of the man pages are case sensitive e.g. _[Ee]xit.2,
{NAN,nan}.3, perhaps others.
I took care of my own system using commands like below, but would appreciate
advice on whether there is any better portable or Cygwin specific approach, and
what are the opinions on the best way to handle this in the cygport for download
and install?
Is this supported by Cygwin on Windows 10 versions >= [20]18-03 with the
directory attribute set, are there likely to be any problems with git, or in
general with POSIX<->Windows file names?
$ cd /usr/share/man/linux/
$ for s in man?; do fsutil file setCaseSensitiveInfo $s; done
Case sensitive attribute on directory ...\usr\share\man\linux\man1 is enabled.
Case sensitive attribute on directory ...\usr\share\man\linux\man2 is enabled.
Case sensitive attribute on directory ...\usr\share\man\linux\man3 is enabled.
Case sensitive attribute on directory ...\usr\share\man\linux\man4 is enabled.
Case sensitive attribute on directory ...\usr\share\man\linux\man5 is enabled.
Case sensitive attribute on directory ...\usr\share\man\linux\man6 is enabled.
Case sensitive attribute on directory ...\usr\share\man\linux\man7 is enabled.
Case sensitive attribute on directory ...\usr\share\man\linux\man8 is enabled.
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next reply other threads:[~2023-02-15 7:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 7:11 Brian Inglis [this message]
2023-02-15 9:22 ` Corinna Vinschen
2023-02-16 5:55 ` Brian Inglis
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=0e730b68-f661-ba13-9020-acce69932067@Shaw.ca \
--to=brian.inglis@shaw.ca \
--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).