peter.kielbasiewicz skrev:
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
Stop beating a dead horse and use dos2unix on your scripts already.
--
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/
