public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: Thomas Wolff <towo@towo.net>, cygwin@cygwin.com
Subject: Re: Problems on case-sensitive file systems
Date: Thu, 23 Oct 2014 22:05:00 -0000	[thread overview]
Message-ID: <63375991.20141024015016@yandex.ru> (raw)
In-Reply-To: <5449390F.5000903@towo.net>

Greetings, Thomas Wolff!

>>>>> I'm facing a number of issues with case-sensitivity which I've collected:
>>>>>
>>>>> There is a documented limitation on case-sensitivity using drive letter
>>>>> paths,
>>>>> also mentioned in https://sourceware.org/ml/cygwin/2013-08/msg00090.html
>>>>> (last item). I vaguely remember seeing a reason for this limitation in some
>>>>> mail but can't find it again. I think it would be good to remove this
>>>>> limitation because it breaks user expectations when working on
>>>>> case-sensitive drives.
>>>> The user expectation when using DOS paths is caseinsensitivity in the
>>>> first place.  But, as usual, there's no way to do this right, since
>>>> somebody will have another POV.  My stance is, don't use DOS paths when
>>>> using Cygwin.  At leats don't use DOS paths if you have any expectations
>>>> about special POSIX path handling on Cygwin.
>>> I use an application that uses Windows or mixed paths, I cannot influence
>>> it. So while I understand your POV, it would still be helpful to have path
>>> interpretation fully-featured. (If you point me to a place in winsup, I
>>> might even try to do something myself.)
>> I'm not going to apply a patch to do that.  DOS paths get no special
>> treatment, they are always handled with DOS/Windows defaults.
> Any last chance to get a distinction here between X:\dos\paths and 
> X:/mixed/paths?

No. It is the same path.


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 24.10.2014, <1:49>

Sorry for my terrible english...


--
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

  reply	other threads:[~2014-10-23 22:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22  7:01 Thomas Wolff
2014-10-22 13:52 ` Eric Blake
2014-10-22 13:55   ` Corinna Vinschen
2014-10-22 14:00 ` Corinna Vinschen
2014-10-23 12:42   ` Thomas Wolff
2014-10-23 15:36     ` Corinna Vinschen
2014-10-23 17:21       ` Thomas Wolff
2014-10-23 22:05         ` Andrey Repin [this message]
2014-10-24  9:55         ` 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=63375991.20141024015016@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=cygwin@cygwin.com \
    --cc=towo@towo.net \
    /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).