DMARC-Filter:	OpenDMARC Filter v1.4.2 delorie.com 559Il0th1663109
Authentication-Results:	delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com
Authentication-Results:	delorie.com; spf=pass smtp.mailfrom=cygwin.com
DKIM-Filter:	OpenDKIM Filter v2.11.0 delorie.com 559Il0th1663109
Authentication-Results:	delorie.com;
	dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=a+R/5Kjm
X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org E9352383069A
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1749494818;
	bh=wUYVLn1UwlUHju6193NIAJ7JEP2JMhrPUM/B/Cic51Y=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	From;
	b=a+R/5Kjm+AGZNEn4S9NQ+5YhWgtmx5PBtO9bT/S/vqwDqvttczpcgSv7UumbGdLij
	It1nk5jAa2lq8h5ez518VCfiDXVmw/FOCgCaO4dxotsjbSVowS+7mvsiDTpPUsJgDa
	iKizScsQNOJmZrh9j4HTcKIE0wcrV4SErzLuaD/E=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.2 sourceware.org B7B833858D38
ARC-Filter:	OpenARC Filter v1.0.0 sourceware.org B7B833858D38
ARC-Seal:	i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1749494752; cv=none;
	b=fZfiipNeL60K6Ja7IlIX9AmOYI50tUQUBPuzqrH9Tw956lWrGvcz4gSJhCg1we8ZkMVeyGmOBniQKte4c01QsFyIZ33V1xsTRi96XP6s7QqHS+PUxh2q23Kd71nOVaCFCjjomQIWWBFC9TDZeFCt4yhz6GM0/r/jSkqQ3N/zDfY=
ARC-Message-Signature:	i=1; a=rsa-sha256; d=sourceware.org; s=key;
	t=1749494752; c=relaxed/simple;
	bh=tTAeQIkW+lrxIIck8XU43zpodumPIyfSf/Wqb5PVLjQ=;
	h=DKIM-Signature:Date:From:To:Subject:Message-ID:MIME-Version;
	b=F30vg79UCMVejKgw6IuEqmEGAohuB8BqhE8dSPizQMBqwjdJekyl8TfbDZW1l/0I2DoY6+NTefwYqDL4GQe6U1ISYQEy9m8tWAJSxwsu4/JvNyQjSwv2ZgxkaQxzEufrdmnZujebm3LcN152TNZ+qPiek7r9PsORifHGd7BSr/4=
ARC-Authentication-Results:	i=1; server2.sourceware.org
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org B7B833858D38
Date:	Mon, 9 Jun 2025 11:45:52 -0700 (PDT)
X-X-Sender:	jeremyd AT resin DOT csoft DOT net
To:	Brian Inglis via Cygwin <cygwin AT cygwin DOT com>
Subject:	Re: RFE: getconf(1)/|pathconf()| support for |_PC_CASE_SENSITIVE| ...
In-Reply-To:	<606031db-b0fc-43ec-bbeb-4a34a001966b@SystematicSW.ab.ca>
Message-ID:	<c3d06f76-e8cc-300b-0ed1-d8b806ddbd68@jdrake.com>
References:	<CAKAoaQ=YrVo4uB0Cqq5hnY1D3N0CjFyjjr1FJ__q9mteeN6zcQ AT mail DOT gmail DOT com>
	<02c18d26-a277-46d6-b25b-b5b216e8daaa AT SystematicSW DOT ab DOT ca>
	<CAKAoaQnb-YoY4CEcBdZ7kWKdqUm-Lu-_SoK8s4vrFvB2zSBDfA AT mail DOT gmail DOT com>
	<85a6c084-c523-769a-2e42-d7e8b0e170d9 AT jdrake DOT com>
	<606031db-b0fc-43ec-bbeb-4a34a001966b AT SystematicSW DOT ab DOT ca>
MIME-Version:	1.0
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.30
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Jeremy Drake via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Jeremy Drake <cygwin AT jdrake DOT com>
Errors-To:	cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>

On Sun, 8 Jun 2025, Brian Inglis via Cygwin wrote:

> On 2025-06-07 19:50, Jeremy Drake via Cygwin wrote:
> > On Sun, 8 Jun 2025, Roland Mainz via Cygwin wrote:
> >
> >> I know... but the request is for portable applications and scripts,
> >> which either use |pathconf(...,_PC_CASE_SENSITIVE)| or /bin/getconf to
> >> probe this information. Both APIs are not supported by Cygwin yet...
> >
> > Isn't it?
>
> I am still unclear if that uses only the kernel or filesystem case sensitivity
> flags or also takes into account the WSL directory case sensitivity?

It does not currently.  The pc.objcaseinsensitive flag is set if the OS is
case insensitive or the filesystem is case insensitive.  I was preparing a
patch to take the same case sensitive flag as lsattr uses for "C" into
account for pathconf, but I am unsure now how the case-sensitive directory
situation actually works out.  It seems like Cygwin would still pass the
OBJ_CASE_INSENSITIVE flag to the OS, I guess it doesn't respect that in a
case-sensitive directory?  Should pathconv check the directory case
insensitive flag when initializing caseinsensitive for the
objcaseinsensitive accessor?

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -