X-Spam-Check-By: sourceware.org Subject: Re: CASE error in script file To: cygwin AT cygwin DOT com Date: Thu, 9 Nov 2006 02:51:15 -0700 (MST) CC: Jim Easton X-Mailer: ELM [version 2.4ME+ PL66 (25)] Message-Id: <20061109095115.8A1F65653D@erskine.cs.ualberta.ca> From: jim AT cs DOT ualberta DOT ca (Jim Easton) X-IsSubscribed: yes 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 Hi Eric, 08 Nov 2006 Eric Blake wrote: ... > Consider upgrading - we're at cygwin 1.5.21 and bash 3.1 (or > experimentally, 3.2). This list does not make it a habit to support older > than the previous release, because of the bugs that have been fixed since. > > > > > Is there a bash variable that controls such behaviour (I can't find one) > > or was there an upgrade in the interim? > > HAVE YOU NOT BEEN READING THE ARCHIVES? This has been the hottest topic > on this list _all month long_. > http://cygwin.com/ml/cygwin-announce/2006-11/msg00009.html Actually, to be honest, no :-). Thanks for the pointer and I have commented my .bashrc file to remind me when I eventually do get around to upgrading. Not that it will bother me personally because I seldom run into DOS style files and never shell scripts. - I was just curious and hoping to learn something. It's no wonder I couldn't find the ignrc option - it doesn't exist in my version. :-) Also, as per Larry Hall, it hurls on linux, solaris and I didn't try any others. Thanks again. Jim Easton -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/