file system name case insensitivity issue: Possible inclusion for the FAQ or User Manual?

Christopher Faylor
Thu May 26 19:36:00 GMT 2011

On Thu, May 26, 2011 at 02:28:53PM -0400, Lee Rothstein wrote:
>Issue: Possible confusing consequences of CYGWIN variable option:
>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.


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


>The transcript, however, indicates the option will not achieve my
>/ $ cd /bin
>/bin $ echo $CYGWIN
>tty title nodosfilewarning glob:noignorecase winsymlinks ntsec
>/bin $ type xwin
>/bin $ which xwin
>/bin $ ls -l xwin
>-rwxrwx--- 1 lr root 2080270 Apr 22 14:45 xwin
>/bin $ ls -l xwin*
>-rwxr-xr-x 1 lr root  24590 Oct 14  2009 xwininfo.exe
>-rwxr-xr-x 1 lr root 172544 Jan 19  2009 xwinwm.exe
># 'rwhich' is a case insensitive regex command finder script,
># I wrote, not a part of the Cygwin distribution
>/bin $ rwhich $ rwhich xwin
>/bin $ ls -l XWin*
>-rwxrwx--- 1 lr root 2080270 Apr 22 14:45 XWin.exe
>/bin $ xwin
><Successfully starts X Windows>
>And, yes, had I thought of it first, I could have used 'file':
>/bin $ file xwin
>xwin: PE32 executable (GUI) Intel 80386 (stripped to external PDB), for 
>MS Windows
>but the capitalization issue remains.
>Finally, I am aware of the change that can be made to the
>registry that will make the file system case sensitive, but I've
>been burned in the past by non-standard changes to the registry,
>and will avoid that.
>BTW, it's little excursions like this that make me value Cygwin
>more, not less. Creating the illusion of a coherent *NIX
>environment on Windows is non-trivial. Thanks, Cygwin developers.
>Problem reports:
>Unsubscribe info:

Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list