X-Spam-Check-By: sourceware.org
Message-ID: <451C93A0.7090203@byu.net>
Date: Thu, 28 Sep 2006 21:31:44 -0600
From: Eric Blake <ebb9@byu.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Thunderbird/1.5.0.7 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: cygwin@cygwin.com, lbreyer@cs.ucsd.edu
Subject: Re: bash 3.1.18 seems seriously broken
References: <451AEBAE.6000703@cs.ucsd.edu> <451B1F43.1030400@byu.net>
In-Reply-To: <451B1F43.1030400@byu.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Eric Blake on 9/27/2006 7:02 PM:
> change the script to ignore whitespace (make the first non-comment line
> set IFS appropriately, as in this snippet:
> IFS=' ''	''
> '

I retract this third suggestion.  On investigation of the bash source,
bash still treats \r as a non-IFS-whitespace, so while it has some effect,
it is not a complete way to ignore \r\n line endings.

I may still be able to add a cygwin-specific shopt for this, but recommend
a text mount in the meantime if you are forced to use \r\n endings.

- --
Life is short - so eat dessert first!

Eric Blake             ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFHJOe84KuGfSFAYARAoSbAKCDfJWh6V5Pt+eMr8FJgwMQisJgEwCfcbiK
xPM7fPRvk4x1m6lZS5/hwLY=
=C8IO
-----END PGP SIGNATURE-----

--
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/

