Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Subject: RE: bash CR and backquotes trouble
Date: Thu, 2 Nov 2006 10:20:40 -0800
Message-ID: <657A9BE009D3504AAE29BD8E8C2DD61E01A5ADBF@SDGEXEVS02.corp.intuit.net>
In-Reply-To: <454A33A8.9050508@adacore.com>
From: "Wilks, Dan" <Dan_Wilks@intuit.com>
To: <cygwin@cygwin.com>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-Transfer-Encoding: 8bit

Nicolas Roche wrote:
> t=`gcc --print-multi-lib` where gcc is a mingw gcc.
> 
> As my gcc is a mingw program, it outputs CR/LFs. In previous versions
> bash used to ignore the CR, so t variable was not containing any CR.
> Now this is no more the case and this is causing some troubles

Looking back to a comment Eric Blake made on 10/23

> igncr only ignores \r in the input file, not in `` or $() command 
> substitution.  But IFS will cover that.  Hmm, maybe I should take a
closer 
> look at command substitution to see if I can make igncr affect that as

> well.  I'll try and get that in bash-3.2-4

Then again on 10/24

> A new release of bash, 3.2-4, is now available for experimental use, 
> replacing 3.2-3. Version 3.1-9 remains as the current version for now.
> ...
> 5. You can also experiment with the IFS variable for controlling how
bash 
> will treat \r during variable expansion.

So you could give the new experimental version of Bash a try.

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