From: cgf AT bbc DOT com (Chris Faylor)
Subject: Re: case insensitive globbing broken
30 Oct 1997 06:35:33 -0800
Message-ID: <EIvArw.1I8.cygnus.gnu-win32@bbc.com>
References: <97Oct29 DOT 164243est DOT 13851 AT gateway DOT intersys DOT com>
Reply-To: cgf AT bbc DOT com
To: gnu-win32 AT cygnus DOT com

In article <97Oct29 DOT 164243est DOT 13851 AT gateway DOT intersys DOT com>,
Jon Willeke  <willeke AT intersys DOT com> wrote:
>Globbing is broken in b18.  I scanned the archives, release notes, and FAQ
>for case sensitivity issues, and I don't think this has been addressed.
>
>If I have two files, foo.tmp and bar.TMP; ls *.tmp only returns foo.tmp.  ls
>bar.tmp, on the other hand, returns bar.tmp.
>
>I first noticed this problem when I grepped a bunch of text files for a
>pattern that I knew was in more than one of them.  grep didn't preface the
>matches with the filenames, because all but one of the files had an
>uppercase extension.  The file with the lowercase extension was the only one
>grep checked.

If you scanned the archives you should have seen a discussion about this
issue.  As a UNIX utility it is debatable that you could consider it
"broken" behavior when bash does not match bar.TMP with a pattern of
*.tmp .  UNIX is case sensitive, after all.

Since bash uses the same globbing functions on UNIX and Windows NT and
since Windows NT does store filenames in mixed case, bash's behavior is
understandable.  I'm not saying that it is desireable or preferred but
it is understandable.

Someone had created a version of bash that was case insensitive.  You might
want to search the archives again to see if you can locate it.
-- 
http://www.bbc.com/	cgf AT bbc DOT com			"Strange how unreal
VMS=>UNIX Solutions	Boston Business Computing	 the real can be."
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".