Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 Message-ID: <95a8830605040208376009ca19@mail.gmail.com> Date: Sat, 2 Apr 2005 08:37:26 -0800 From: beau Reply-To: beau To: cygwin@cygwin.com Subject: Re: revisiting case sensitivity In-Reply-To: <040220050428.23864.424E1F5F000E79ED00005D3822007340760A050E040D0C079D0A@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <040220050428.23864.424E1F5F000E79ED00005D3822007340760A050E040D0C079D0A@comcast.net> On Apr 1, 2005 8:28 PM, Eric Blake 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/