Message-ID: <45509C9D.5090402@adacore.com>
Date: Tue, 07 Nov 2006 15:47:57 +0100
From: Nicolas Roche <roche@adacore.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: bash CR and backquotes trouble
References: <454A2CE4.7030805@adacore.com> <454A3DC0.9040305@cygwin.com> <454A33A8.9050508@adacore.com> <454A47CD.50009@cygwin.com> <454A3BB4.3060808@adacore.com> <454A5E6E.9020704@cygwin.com> <45508870.9090603@adacore.com> <45508B99.5040904@byu.net> <45508FC1.3050105@byu.net>
In-Reply-To: <45508FC1.3050105@byu.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Eric Blake a écrit :
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> According to Eric Blake on 11/7/2006 6:35 AM:
>   
>> Have you tried the experimental bash-3.2.3-5, and exporting SHELLOPTS in
>> your environment with igncr specified?  Within bash, SHELLOPTS is
>> read-only, but reflects the current shell option settings, so you merely
>> need export it so that it is in the environment instead of a shell local
>> variable.
>>     
>
> A slight clarification: once in bash, the read-only SHELLOPTS only tracks
> actions involving 'set -o', it does not track actions involving 'shopt -s'
> or other back doors to affecting shell options.  I noticed this with the
> 'history' shell option as well as the 'igncr' shell option, so it is not
> cygwin-specific; however, I'm not sure whether to call it a bug or a
> feature in upstream handling of how SHELLOPTS is handled.
>   

Thanks for the tip. Working also with 3.2.1(4). I am not using shopt in 
scripts so everything should be OK.

Just one last question, when 3.2 is planned to be push in the mainstream 
(i.e not experimental)

Thanks to everyone for the help

Nicolas


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