This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: Filenames with Win32 special characters (or: Interix filename compatibility)
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin-developers at cygwin dot com
- Date: Fri, 11 Jul 2008 15:18:40 +0200
- Subject: Re: Filenames with Win32 special characters (or: Interix filename compatibility)
- References: <20080311101048.GY18407@calimero.vinschen.de> <47D661B8.BE70217F@dessent.net> <20080311105017.GB18407@calimero.vinschen.de> <20080311105545.GC18407@calimero.vinschen.de> <20080311163143.GB10850@ednor.casa.cgf.cx> <20080311182517.GI18407@calimero.vinschen.de> <20080702125019.GP5038@calimero.vinschen.de>
- Reply-to: cygwin-developers at cygwin dot com
On Jul 2 14:50, Corinna Vinschen wrote:
> Two months later, here's a question: Should we start to allow real case
> sensitivity? Changing the above registry key is not exactly rocket
> science. I had this idea to change the definition of non-managed and
> managed mounts like this:
>
> - non-managed means case-insensitive and not converting chars to the
> UNICODE Private Use Area. This means sticking to good old Win32
> compatibility.
>
> - managed means, all file operation are using case-sensitivity and
> special chars (:,<,>) are converted to the Private Use Area.
> Still, that won't work with fork/exec, due to using the Win32
> function CreateProcess.
If nobody has an opinion, I'll implement it as above and we can just
see how it works out. It's not really tricky, just conditional path
case matching and setting a flag in calls to InitializeObjectAttributes.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat