X-Spam-Check-By: sourceware.org
Message-ID: <452EA386.9010201@qualcomm.com>
Date: Thu, 12 Oct 2006 13:20:22 -0700
From: Rob Walker <rwalker AT qualcomm DOT com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: shopt igncr not working
References: <1160655422743 DOT antti DOT nospam DOT 1605718 DOT wGO_WJ9D1NlId3tB-z6Qig AT luukku DOT com> <20061012123406 DOT GA30908 AT trixie DOT casa DOT cgf DOT cx>
In-Reply-To: <20061012123406.GA30908@trixie.casa.cgf.cx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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

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/