Date:	Thu, 30 Jan 2003 09:53:33 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	djgpp AT delorie DOT com
Subject:	Re: Command line wildcard expansion under Win2K
In-Reply-To:	<3e38c547.sandmann@clio.rice.edu>
Message-ID:	<Pine.SUN.3.91.1030130095126.2797A-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Thu, 30 Jan 2003, Charles Sandmann wrote:

> On MSDOS, filenames are always matched case-insensitively.  On
> filesystems that preserve letter-case in filenames (such as Windows 9x),
> matches are case-insensitive UNLESS THE PATTERN INCLUDES UPPERCASE
> CHARACTERS. (my caps)
> 
> So, if you use any upper case characters on your input you may be
> surprised.  I believe this is the behavior which is non-intuitive.

Could you please state explicitly, with examples, what is non-intuitive 
about this, and what alternative behavior would be more intuitive?

> There are some good reasons for this behavior, but I agree it would be
> nice in many applications to be able to turn it off case sensitive
> matching and still be able to return the lowercased names when 
> appropriate.

Sorry, I'm not sure I understand this (I think there's a typo in this 
sentence): what would you like to be able to do?

- Raw text -