From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Detecting case sensitivity
Date: Thu, 20 Oct 2016 01:34:00 -0000 [thread overview]
Message-ID: <581c601a-b2cd-b6e6-7106-6a98d95eb117@cornell.edu> (raw)
In-Reply-To: <20161019111049.GA4801@calimero.vinschen.de>
On 10/19/2016 7:10 AM, Corinna Vinschen wrote:
> On Sep 20 18:03, Ken Brown wrote:
>> I found an old discussion
>> (https://www.cygwin.com/ml/cygwin/2007-08/msg00594.html) about the
>> possibility of adding a _PC_CASE_INSENSITIVE flag to pathconf. Has anyone
>> thought further about this? I would find this useful for emacs[*].
>>
>> I've taken a quick look at the pathconf code, and it looks like it wouldn't
>> be difficult to add this. I could try to provide a patch if the powers that
>> be would be receptive.
>
> /me marks herself as being receptive
Should the getconf utility be patched to support the new
_PC_CASE_INSENSITIVE flag? I'm asking because getconf doesn't currently
support the Cygwin-only flags _PC_POSIX_PERMISSIONS and
_PC_POSIX_SECURITY. This seems to contradict the documentation at
https://cygwin.com/cygwin-ug-net/getconf.html:
"...getconf serves as a wrapper for the pathconf function, supporting
the symbolic constants defined in the unistd.h header, without the _PC_
prefix."
If the omission of _PC_POSIX_PERMISSIONS and _PC_POSIX_SECURITY was just
an oversight, I can add support for them along with my patch.
Ken
--
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-10-19 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 23:54 Ken Brown
2016-10-19 11:27 ` Corinna Vinschen
2016-10-20 1:34 ` Ken Brown [this message]
2016-10-20 13:52 ` 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=581c601a-b2cd-b6e6-7106-6a98d95eb117@cornell.edu \
--to=kbrown@cornell.edu \
--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).