From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12824 invoked by alias); 26 May 2011 18:29:44 -0000 Received: (qmail 12814 invoked by uid 22791); 26 May 2011 18:29:43 -0000 X-SWARE-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,BAYES_00,RDNS_NONE,SPF_HELO_PASS,TW_RW,TW_WX,TW_XR X-Spam-Check-By: sourceware.org Received: from Unknown (HELO simon.codemeta.com) (199.125.75.14) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 26 May 2011 18:29:21 +0000 Received: from [192.168.1.101] (c-66-31-207-108.hsd1.nh.comcast.net [66.31.207.108]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by simon.codemeta.com (Postfix) with ESMTP id 1CB43708CE for ; Thu, 26 May 2011 14:29:14 -0400 (EDT) Message-ID: <4DDE9BE5.90105@veritech.com> Date: Thu, 26 May 2011 18:29:00 -0000 From: Lee Rothstein User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: "Cygwin, eMail List" Subject: file system name case insensitivity issue: Possible inclusion for the FAQ or User Manual? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2011-05/txt/msg00398.txt.bz2 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. The transcript, however, indicates the option will not achieve my aim. -- / $ cd /bin /bin $ echo $CYGWIN tty title nodosfilewarning glob:noignorecase winsymlinks ntsec /bin $ type xwin /bin/xwin /bin $ which xwin /bin/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 /local/Scripts/start_xwin.old /bin/dmxwininfo.exe /bin/lyxwin.exe /bin/startxwin.exe /bin/XWin.exe /bin/xwininfo.exe /bin/xwinwm.exe /bin $ ls -l XWin* -rwxrwx--- 1 lr root 2080270 Apr 22 14:45 XWin.exe /bin $ xwin -- -- 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. Lee -- 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