www.delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2006/10/12/23:08:56

X-Spam-Check-By: sourceware.org
Date: Thu, 12 Oct 2006 23:08:39 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: shopt igncr not working
Message-ID: <20061013030839.GB14483@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
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> <20061012212011 DOT GA8535 AT trixie DOT casa DOT cgf DOT cx> <452EFDDB DOT 1010301 AT qualcomm DOT com>
Mime-Version: 1.0
In-Reply-To: <452EFDDB.1010301@qualcomm.com>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Thu, Oct 12, 2006 at 07:45:47PM -0700, Rob Walker wrote:
>Christopher Faylor wrote:
>>On Thu, Oct 12, 2006 at 01:20:22PM -0700, Rob Walker wrote:
>>>Christopher Faylor wrote:
>>>>On Thu, Oct 12, 2006 at 03:17:02PM +0300, Antti Tyrv?inen wrote:
>>>>>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?
>>
>>So, why were you asking for help if you weren't going to actually avail
>>yourself of it?
>>  
>Don't get me wrong.  Cygwin's the best Linux-like environment I've ever 
>used.  Barring a fix, a workaround is what I'll employ if possible.  But 
>each workaround adds to the tribal knowledge base, making Cygwin harder 
>to sell to my teams.  Up until recently I'd tell them to just "go get 
>the latest Cygwin" and everything will work.

Sorry.  I thought you were the person who was asking for help.  Checking
the thread in the archives, I see that you weren't.

I hope that the OP will avail himself of my advice.

cgf

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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019