From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28791 invoked by alias); 21 Sep 2006 03:37:10 -0000 Received: (qmail 28782 invoked by uid 22791); 21 Sep 2006 03:37:10 -0000 X-Spam-Check-By: sourceware.org Received: from ns1.anodized.com (HELO ns1.anodized.com) (204.15.208.61) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 21 Sep 2006 03:37:08 +0000 Received: from ns1.anodized.com (localhost [127.0.0.1]) by ns1.anodized.com (8.13.1/8.13.1) with ESMTP id k8L3b6cr006852 for ; Wed, 20 Sep 2006 20:37:06 -0700 Received: from 127.0.0.1 ([127.0.0.1] helo=ns1.anodized.com) by ASSP-nospam; 20 Sep 2006 20:37:06 -0700 Received: (from clayne@localhost) by ns1.anodized.com (8.13.1/8.13.1/Submit) id k8L3b6de006849 for cygwin@cygwin.com; Wed, 20 Sep 2006 20:37:06 -0700 Date: Thu, 21 Sep 2006 03:37:00 -0000 From: Christopher Layne To: cygwin@cygwin.com Subject: Re: bash-3.1-7　BUG Message-ID: <20060921033706.GB6790@ns1.anodized.com> References: <091320060438.11140.45078B490008FD8600002B8422007610640A050E040D0C079D0A@comcast.net> <20060913052510.GB1256@trixie.casa.cgf.cx> <45089854.8010705@scytek.de> <20060914001902.GB24899@trixie.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060914001902.GB24899@trixie.casa.cgf.cx> User-Agent: Mutt/1.5.11 X-Assp-Spam-Prob: 0.00000 X-Assp-Whitelisted: Yes X-Assp-Envelope-From: clayne@ns1.anodized.com X-Assp-Intended-For: cygwin@cygwin.com X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2006-09/txt/msg00421.txt.bz2 On Wed, Sep 13, 2006 at 08:19:02PM -0400, Christopher Faylor wrote: > As long as you have Corinna or myself in charge we are going to stick > with the whole "Linux on Windows" thing. If bash doesn't like \r\n line > endings on Linux, if we purposely recommend against using text mode > files, and if we can see noticeable performance improvements in bash > from not honoring \r\n line endings, then bash should definitely be > using the "binmode" code. Yep. Ridiculous performance improvements at that. > > If Eric cares enough to make \r\n shell scripts work in bash, then more > power to him. If he doesn't then I have no problem with releasing a > bash that hiccups on files which use \r\n and informing people that they > should fix their scripts. > > cgf Totally agreed here too. I've been using my splintered off bash build for weeks now. Haven't really had any issues - however I also explicitly do not use text mode mounts or any related nonsense. -cl -- 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/