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
