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
Message-ID:	<95a8830605040208376009ca19@mail.gmail.com>
Date:	Sat, 2 Apr 2005 08:37:26 -0800
From:	beau <phaedral AT gmail DOT com>
Reply-To:	beau <phaedral AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: revisiting case sensitivity
In-Reply-To:	<040220050428.23864.424E1F5F000E79ED00005D3822007340760A050E040D0C079D0A@comcast.net>
Mime-Version:	1.0
References:	<040220050428 DOT 23864 DOT 424E1F5F000E79ED00005D3822007340760A050E040D0C079D0A AT comcast DOT net>

On Apr 1, 2005 8:28 PM, Eric Blake <ericblake AT comcast DOT net> wrote:
> Does this corner case warrant an upstream request in coreutils to
> gracefully handle this?
We have gone so very far over my head that I can't even pretend to
have a right to an opinion (but when did *that* ever stop anyone from
sharing?)  I'll probably just handle my own issues with a perl script;
I'm slightly less an l-user with perl than with bash (but only
slightly!)  Truth is, I tried Igor's solution and it just froze my
cygwin (the rxvt from which I called it and any subsequent rxvt
opened) and I'm not bash-or-cygwin-savvy enough to see what is wrong.

That said, my failure to grok this is no reflection on the goodness
that is cygwin.  Rock on.

beau

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