X-Spam-Check-By: sourceware.org Date: Thu, 12 Oct 2006 23:08:39 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: shopt igncr not working Message-ID: <20061013030839.GB14483@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <1160655422743.antti.nospam.1605718.wGO_WJ9D1NlId3tB-z6Qig@luukku.com> <20061012123406.GA30908@trixie.casa.cgf.cx> <452EA386.9010201@qualcomm.com> <20061012212011.GA8535@trixie.casa.cgf.cx> <452EFDDB.1010301@qualcomm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <452EFDDB.1010301@qualcomm.com> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.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/