Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <19990604010334.A4770@ba.best.com> Date: Fri, 4 Jun 1999 01:03:34 -0400 From: Glenn Spell To: cygwin AT sourceware DOT cygnus DOT com Subject: Re: 'find' case insensitive filenames Mail-Followup-To: cygwin AT sourceware DOT cygnus DOT com References: <015d01beae34$e0297ba0$1400000a AT yjlee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <015d01beae34$e0297ba0$1400000a@yjlee>; from "Yu-Jui Lee" on Fri, Jun 04, 1999 at 10:49AM Organization: the aerie On Jun 04 1999 about 10:49AM +0800, Yu-Jui Lee wrote: > This may be a stray topic. But in a Win32 environment, the > convention with file names is case insensitive. ... and case preserving. > While the 'find' command in cygwin b20.1 is case sensitive. Cygwin B20.1 'find' is GNU 'find' version 4.1. The manual is available at . GNU 'find' has both case-sensitive and case-insensitive versions of the following tests for patterns: -name/-iname -path/-ipath -regex/-iregex. > For example, if I want to find a case-insensitive "foo.bar", I > need to type "find . -name "[Ff][Oo][Oo][Bb][Aa][Rr]". Is there a > convenient way to do this? find . -iname "foo*" | grep -i bar -glenn -- ) Glenn Spell ) _ _____ ) Fayetteville, North Carolina, C. S. A. )_ (__\____o /_/_ | ) _ _ _ _ _ _ _ _ _ _ _ _ _ _ ) >-----._/_/__]> )- blue skies - happy trails - sweet dreams -) `0 | -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com