X-Spam-Check-By: sourceware.org
Message-ID: <452EC120.A76763A0@dessent.net>
Date: Thu, 12 Oct 2006 15:26:40 -0700
From: Brian Dessent <brian AT dessent DOT net>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
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> <452EA386 DOT 9010201 AT qualcomm DOT com> <452EA8DD DOT 1070108 AT kionka DOT org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
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

*sigh*

"Daniel P. Kionka" wrote:

> I cannot track down every
> bash script and add "shopt -s igncr", and no one should ever have to.

Of course not.  That is a silly way to deal with the issue.  One of the
points of this whole conflagration is to get people to realize that if
they are dealing with files with CRLF line endings then they need to be
using textmode mounts.  If you do this then everything should work fine
without having to modify any scripts.

If anything it should be considered a good thing that these changes
alerted you to the fact that you were mixing binmode and CRLF line
endings, much like coal miners were happy when their canary died because
it signaled to them that they need to GTFO ASAP.

And even if textmode for some reason is not an option, you could have
used the BASH_ENV environtment variable as Eric pointed out in
<http://cygwin.com/ml/cygwin/2006-10/msg00145.html>.  This causes a
site-wide enabling of igncr without having to individually edit
anything.

> If a new version of a program is incompatible, it should be renamed as a
> new program, like baash (bourne again again shell).

It's not incompatible.  It just is not as tolerant of incorrect
operating parameters.  Don't interpret this as meaning "Cygwin doesn't
support CRLF", it means "Cygwin does not support CRLF when textmode is
not used".  By the way this was done because it resulted in a
significant performance increase in an area that has traditionally been
painfully slow in Cygwin, running large configure scripts.

> I am disappointed with the developer response.  They insist that the
> "right" solution is to remove CRs.  Cygwin is not just a project for
> Unix nerds anymore!  I love Unix, too, but I accept that Windows uses
> CR/LF.  Bash scripts are text files; you must be able to edit them with
> notepad, and when you check them into source control, they get checked
> out with CR/LF like all text files.

Again, "remove CRs" is one option but not the only one.  This is
precisely what textmode was designed for, and it should work fine when
used correctly.

Brian

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