X-Spam-Check-By: sourceware.org
Date: Wed, 7 Feb 2007 09:00:49 +0100 (MET)
From: "peter.kielbasiewicz" <praktpk AT bbl DOT ms DOT philips DOT com>
Message-Id: <200702070800.JAA03397@bmdme9.bbl.ms.philips.com>
To: cygwin AT cygwin DOT com
Subject: late bash CR/LF functionality change problem
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit
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

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.

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.

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.

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.

Is there an quick and easy solution to the problem out yet?

Peter



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