Date:	Wed, 29 Jan 2003 08:03:29 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Charles Sandmann <sandmann AT clio DOT rice DOT edu>
cc:	djgpp AT delorie DOT com
Subject:	Re: Command line wildcard expansion under Win2K
In-Reply-To:	<3e373fe8.sandmann@clio.rice.edu>
Message-ID:	<Pine.SUN.3.91.1030129080002.11962C@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 Tue, 28 Jan 2003, Charles Sandmann wrote:

> I see this behavior.  For example, "A.vec" exists (A upper case):
> 
> C:\>djecho a*.vec A*.vec A*.VEC a*.VEC
> a.vec A.vec A*.VEC a*.VEC
> 
> This behavior is not Win2K specific - it also happens on Win98
> 
> "B.VEC" exists (all upper case):
> 
> C:\>djecho b*.vec B*.vec b*.VEC B*.VEC
> b.VEC B*.vec b*.VEC B.VEC                    (on Win98, either build)
> B.VEC B*.vec b*.VEC B.VEC                    (Win2K, v2.03 refresh)
> b.vec B*.vec b*.VEC B.VEC                    (Win2K, CVS build)

I think this is the intended behavior.  The docs of `glob' should 
describe it.  In particular, file names that fit 8+3 DOS limits (like 
B.VEC in this case) are downcased by default.

> It is certainly not what I would expect.  

Even after reading the docs?  If so, why not?  Does setting "FNCASE=y" 
change the behavior to something that you like better?

- Raw text -