This is the mail archive of the
mailing list for the Cygwin project.
RE: Similar Bash 3.1.18 CR/LF Problem
- From: "Williams, Gerald S \(Jerry\)" <gsw at agere dot com>
- To: <cygwin at cygwin dot com>
- Date: Wed, 4 Oct 2006 13:06:19 -0400
- Subject: RE: Similar Bash 3.1.18 CR/LF Problem
Christopher Faylor wrote:
> The dilemma here is that I read other mailing lists besides
> cygwin where people are trying to use Cygwin but are close
> to giving up because it is so slow. So, making bash faster
> for people who are using it correctly is very desirable.
Which is why we need to get the patch in upstream. If you
can't make it faster, you can at least make what you're
comparing against slower. :-)
Seriously, I'd have a hard time believing that supporting
<CR><LF> endings would noticably impact performance if it
were done as part of upstream BASH. Special-casing Cygwin
(especially when you start doing things like checking for
DOS paths, examining the first line, etc.) would impact
performance, surely. So I agree--don't do that.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html