Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Injected-Via-Gmane: http://gmane.org/ To: cygwin AT cygwin DOT com From: John Williams Subject: Re: file name case sensitivity Date: Tue, 25 Feb 2003 15:09:11 +1000 Lines: 24 Message-ID: References: <067c01c2dc8a$b7174bb0$c67486d9 AT webdev> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet AT main DOT gmane DOT org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210 X-Accept-Language: en-us, en In-Reply-To: <067c01c2dc8a$b7174bb0$c67486d9@webdev> Hi Elfyn, > No. You can use the check_case option in the CYGWIN environment variable, > but that'll only get you half way to what you want. Take a look at > () to see how it works > and how to use it. Thanks for that. As you predict, check_case can't undo the evil that is causing my problem in the first place. My loathing goes in equal measures to Microsoft for failing after 20 years to support case-sensitive file names, and whomever it was in the linux dev group who decided it would be a good idea to duplicate some files but only change the filename capitalisation... bleughhh... the conspiracy theorist in me wonders if it was deliberate to kybosh those working under Windows... :O Cheers, John -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/