public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: file system name case insensitivity issue: Possible inclusion for the FAQ or User Manual?
Date: Fri, 27 May 2011 05:30:00 -0000	[thread overview]
Message-ID: <20110527052926.GE28752@calimero.vinschen.de> (raw)
In-Reply-To: <4DDEB0BA.9030903@veritech.com>

On May 26 15:57, Lee D. Rothstein wrote:
> On 5/26/2011 3:35 PM, Christopher Faylor wrote:
> >On Thu, May 26, 2011 at 02:28:53PM -0400, Lee Rothstein wrote:
> >>Issue: Possible confusing consequences of CYGWIN variable option:
> >>glob:noignorecase
> >>
> >>What follows is an edited transcript of my confusion about trying
> >>to find the command "xwin" (and eventual resolution), having
> >>forgotten about its capitalization. More specifically, I was
> >>trying to figure out if it was a binary or a script (not having
> >>used X in the last year, or so).
> >>
> >>BTW, the reason I had glob:noignorecase set was to catch
> >>capitalization errors on HTML file names I develop for a
> >>LAMP server.
> >Re: http://cygwin.com/cygwin-ug-net/using-cygwinenv.html
> >
> >   (no)glob[:ignorecase] - if set, command line arguments containing
> >   UNIX-style file wildcard characters (brackets, question mark, asterisk,
> >   escaped with \) are expanded into lists of files that match those
> >   wildcards.  This is applicable only to programs running from a DOS
> >   command line prompt.  Default is set.
> >
> >There was no DOS command line prompt in anything below.
> >
> True. So, you're saying that 'glob:noignorecase' had no effect on
> the commands executed. Then the issue that the transcript reveals
> is that in Cygwin, case sensitivity only affects filename specs
> if globbing is used. That may, in fact, have been covered somewhere
> in the documentation. (?)

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.

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


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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  5:30 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 [this message]
2011-05-27 15:53       ` File Name Case Sensitivity & Globbing! Was: " Lee D. Rothstein
2011-05-27 16:12         ` 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=20110527052926.GE28752@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.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).