public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Michael Enright <mike@kmcardiff.com>
To: cygwin@cygwin.com
Subject: Re: Question about incorrect System path from cygpath with case-sensitivity enabled
Date: Sat, 02 Jan 2016 20:34:00 -0000	[thread overview]
Message-ID: <CAOC2fq_SM3Ja5-vgf+T9QPGu0FAjrTw6pe_e0b2t4t39szxbNA@mail.gmail.com> (raw)
In-Reply-To: <B9C70902-5C7E-4AC6-A63A-583DCEC2771C@mac.com>

On Fri, Jan 1, 2016 at 1:21 PM, Bryan Henry wrote:
>
> [~]$ cygpath -S -u
> /C/WINDOWS/System32
> [~]$ file `cygpath -S -u`
> /C/WINDOWS/System32: cannot open `/C/WINDOWS/System32' (No such file or directory)
> [~]$ file /C/Windows/System32
> /C/Windows/System32: directory
>

Although I haven't enabled case-sensitivity I noticed the following:

In power shell, the value of $env.Path is reported with windows
directories where the windows directory is given all in lower case.
But in the same shell, the name of the Windows directory given by "ls
\" is spelled "Windows". I find that to most likely be the spelling of
the directory entry because "ls" seems to faithfully report directory
names in the case given by whatever created the directory in the first
place, instead of some affectation of "ls" capitalizing things.

In Cygwin,
$ cygpath -S -u
/cygdrive/c/windows/System32

I'm running Win10/64 and 64-bit cygwin.

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

      parent reply	other threads:[~2016-01-02 20:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-01 21:21 Bryan Henry
2016-01-02 15:35 ` Andrey Repin
2016-01-08  2:14   ` Corinna Vinschen
2016-01-11  9:26     ` Bryan Henry
2016-01-11  9:38       ` Bryan Henry
2016-01-11 11:55       ` Corinna Vinschen
2016-01-02 20:34 ` Michael Enright [this message]

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=CAOC2fq_SM3Ja5-vgf+T9QPGu0FAjrTw6pe_e0b2t4t39szxbNA@mail.gmail.com \
    --to=mike@kmcardiff.com \
    --cc=cygwin@cygwin.com \
    /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).