From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29501 invoked by alias); 27 May 2011 15:53:57 -0000 Received: (qmail 29490 invoked by uid 22791); 27 May 2011 15:53:57 -0000 X-SWARE-Spam-Status: No, hits=-0.6 required=5.0 tests=AWL,BAYES_00,PLING_QUERY,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from simon.codemeta.com (HELO simon.codemeta.com) (199.125.75.14) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 27 May 2011 15:53:39 +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 1B514708CE for ; Fri, 27 May 2011 11:53:38 -0400 (EDT) Message-ID: <4DDFC8EC.8060507@veritech.com> Date: Fri, 27 May 2011 15:53:00 -0000 From: "Lee D. 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@cygwin.com Subject: File Name Case Sensitivity & Globbing! Was: file system name case insensitivity issue: Possible inclusion for the FAQ or User Manual? References: <4DDE9BE5.90105@veritech.com> <20110526193553.GB6015@ednor.casa.cgf.cx> <4DDEB0BA.9030903@veritech.com> <20110527052926.GE28752@calimero.vinschen.de> In-Reply-To: <20110527052926.GE28752@calimero.vinschen.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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/msg00429.txt.bz2 > 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