X-Spam-Check-By: sourceware.org
Message-ID: <452318BF.3040806@byu.net>
Date: Tue, 03 Oct 2006 20:13:19 -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
Subject: Re: Bash and CR/LF line-endings
References: <004801c6e74b$4c0ef550$33e0f9a0@cr5lsdev>
In-Reply-To: <004801c6e74b$4c0ef550$33e0f9a0@cr5lsdev>
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 Kazuyuki Hagiwara on 10/3/2006 6:23 PM:
> How about  using BASH_ENV variable.
> In the startup script defined by BASH_ENV variable,
> you can put a line "shopt -s igncr".

BASH_ENV already has a defined meaning that conflicts with your
suggestion; read 'man bash' once more.

But bash does have the -O and +O command line option for choosing prior to
script execution what any shopt setting should be.  In other words,

bash -O igncr script_with_cr_lf

will guarantee execution of the script with \r ignored (at least, up until
the script does something to change that shopt).

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

iD8DBQFFIxi/84KuGfSFAYARAgzlAKC+h9w9x6Fo1AfzRcZVAeiMpJgLXwCfQ8y6
H5QDRq7V43q7R2MH2qRKENQ=
=EojF
-----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/

