Re: Filenames with Win32 special characters (or: Interix filename compatibility)

[Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>]

On Fri, Jul 11, 2008 at 03:18:40PM +0200, Corinna Vinschen wrote:
>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.

I've been meaning to give my opinion.  Here it is:

I am uncomfortable with changing things on a global basis like this but
if we do it within cygwin and it is easy to switch back and forth then
that would be ok, at least for experimentation.

cgf