X-Spam-Check-By: sourceware.org
Message-ID: <45C9C5CF.8090002@sh.cvut.cz>
Date: Wed, 07 Feb 2007 13:27:59 +0100
From: =?ISO-8859-1?Q?V=E1clav_Haisman?= <v DOT haisman AT sh DOT cvut DOT cz>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: late bash CR/LF functionality change problem
References: <200702070800 DOT JAA03397 AT bmdme9 DOT bbl DOT ms DOT philips DOT com>
In-Reply-To: <200702070800.JAA03397@bmdme9.bbl.ms.philips.com>
Content-Type: multipart/signed; micalg=pgp-sha1;  protocol="application/pgp-signature";  boundary="------------enig42D9AB62E8C1A7922EB2CE70"
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

--------------enig42D9AB62E8C1A7922EB2CE70
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

peter.kielbasiewicz wrote:
> I recently updated to the latest bash rev. only to find that most of
> my scripts do not work anymore. I browsed through the FAQ and mailing
> lists and found many people having problems with the changed
> behaviour of treating \r literally.
>=20
> I do not want to argue what is right or wrong though. Fact is that
> bash until fall last year functioned in a certain way. Many people
> wrote scripts using this functionality. Now bash functions
> differently which breaks a lot of jobs.
>=20
> Especially batch processes which did their job silently in the
> background all over the sudden cause problems. If a change is
> implemented which has such a big impact it should NEVER be
> implemented as the default behaviour. Instead this new functionality
> should be activated by an env setting, start parameter or the like so
> that the functionality stays backward compatible.
>=20
> What made things even worse is that there is no notification about
> the changed behaviour. It is just the symptoms and everyone
> experiencing the problem must then dig to find out the cause.
The change in bash's behaviour has been announced many times in bash
package release announcements which are sent into this mailing list.
There even was a transition period when it was only part of experimental
bash package. If you have read any of the announcements you would know
about it.

Reading this mailing list is important. It is the only information
channel from Cygwin developers and package maintainers to you, the users.

>=20
> Is there an quick and easy solution to the problem out yet?
Use the d2u utility on your scripts.

>=20
> Peter

--
Vaclav Haisman


--------------enig42D9AB62E8C1A7922EB2CE70
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQEVAwUBRcnF2kNOZDESBK8FAQLKGgf6AnkZNjWbHwQc7lEmxtT2hIHSJXagQiiu
lsb6N2xEvABaQ0tQ35Cm8yrh53aineX0aXutNvoHvykqu+/rInNNUnrge0WxaN+k
l55svQvwtFUrW2sPJp+aHD+jRth/QwgkkyQObAl7DPCw9nsz5ouhkaiSg6I1VDDe
pHxl2ZZa7HgoZ/Vyoer4v7xtpvf9PHedKz0Og6O4srsWYKcZTDPog9XakV9CNxft
aM5Se1gUVC5dDDkGbJDXgvfMFfFCeTDRdpCzsNB1XbNANRhEnqicSInAEg9C7PNW
W5fnZG52yV3MjUfgt3Wz7n5BEwJL6wmoqFOl7xUjk2MKd5qtrtqHzg==
=PGbN
-----END PGP SIGNATURE-----

--------------enig42D9AB62E8C1A7922EB2CE70--