shopt igncr not working

Rob Walker rwalker@qualcomm.com
Thu Oct 12 20:18:00 GMT 2006


Christopher Faylor wrote:
> On Thu, Oct 12, 2006 at 03:17:02PM +0300, Antti Tyrv?inen wrote:
>   
>> Hi!
>>
>> Installed latest cygwin and I met problems with bash and scripts which are in DOS format.
>>
>> $ bash --version
>> GNU bash, version 3.1.17(9)-release (i686-pc-cygwin)
>> Copyright (C) 2005 Free Software Foundation, Inc.
>>
>> I read the mailing lists and I also tried to add ' shopt -s igncr;#' in the beginning of the script, but it didn't work.  In my opinion, this is bad solution if I have to edit all my existing scripts.
>>
>> All works fine with bash 3.1.6.
>>
>> What I should do?
>>
>> a) install bash 3.1.6 and wait for new
>> b) install bash 3.1.9. and convert all my scripts to UNIX format
>>     
>
> b), i.e., use the tool the way it was designed to be used.
>
>   
Saying cygwin's bash wasn't designed to handle CRLF is a lot like saying 
that cygwin's bash (as previously released all these years) wasn't 
designed to work with the rest of Windows.  This might actually be the 
case, but I don't understand the point.  If you don't want to work with 
Windows, why release for Windows?

Many, many other cross-platform products make allowances for CRLF 
(version control systems are a prime example) to maximize compatibility, 
and thereby their usefulness, on Windows.  Cygwin's recent changes (with 
make and bash) here has put a real crimp in my plans to depend on cygwin 
for a portable build environment.

Just curious, is there a goal or strategy that drives changes like this?

Thanks,
Rob


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



More information about the Cygwin mailing list