public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Lee D. Rothstein" <l1ee057@veritech.com>
To: cygwin@cygwin.com
Subject: File Name Case Sensitivity & Globbing! Was: file system name case insensitivity issue: Possible inclusion for the FAQ or User Manual?
Date: Fri, 27 May 2011 15:53:00 -0000	[thread overview]
Message-ID: <4DDFC8EC.8060507@veritech.com> (raw)
In-Reply-To: <20110527052926.GE28752@calimero.vinschen.de>

 > You got that wrong. The CYGWIN=glob:... option only affects how
 > globbing is performed on the command line arguments if the Cygwin
 > process has been started from a native Windows process.  Full stop.

I acknowledged *my* MISTAKE. I do so again.

 > Now, actual filename case sensitivity is an entirely different issue.
 > This is handled by a registry setting, the ability of the underlying
 > filesystems to handle filenames case sesitive, and the settings of
 > the Cygwin mount point:
 >
 > 
http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive
 > http://cygwin.com/cygwin-ug-net/using.html#mount-table

I acknowledged this point as well in my initial post, and why I reject it.

The point remains:

   Globbing is case sensitive while full command name
     invocation/full filename use is not. And, you may never have
     been confused by that, but I maintain it's very confusing. I'm
     not asking that it be "fixed", I'm asking that it be carefully
     documented, and I'm not asking anyone but me to do it. If it is
     so documented, I missed it. And, I read and reread that part of
     the manual before posting both times.

I offered an example session transcript that made that perfectly
clear, and I am willing to write that up however you want it.
Thus far, you've made clear you don't want it. No further replies
will be required if my last "read" is correct.


--
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:[~2011-05-27 15:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-26 18:29 Lee Rothstein
2011-05-26 19:36 ` Christopher Faylor
2011-05-26 19:58   ` Lee D. Rothstein
2011-05-27  5:30     ` Corinna Vinschen
2011-05-27 15:53       ` Lee D. Rothstein [this message]
2011-05-27 16:12         ` File Name Case Sensitivity & Globbing! Was: " Corinna Vinschen
2011-05-27 17:39         ` Thorsten Kampe
2011-05-27 21:36           ` Edward McGuire
2011-05-27 22:46             ` Thorsten Kampe
2011-05-28  7:51             ` Corinna Vinschen
2011-05-28 19:03               ` Christopher Faylor

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=4DDFC8EC.8060507@veritech.com \
    --to=l1ee057@veritech.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).