From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Command line wildcard expansion under Win2K
Date: Thu, 30 Jan 2003 21:28:44 CST
Organization: Rice University, Houston TX
Lines: 16
Message-ID: <3e39ed6c.sandmann@clio.rice.edu>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1030130095126 DOT 2797A-100000 AT is> <3e394a9a DOT sandmann AT clio DOT rice DOT edu> <b1c3go$5d2$1 AT sass2141 DOT sandia DOT gov> <3791-Thu30Jan2003235135+0200-eliz AT is DOT elta DOT co DOT il>
NNTP-Posting-Host: clio.rice.edu
X-Trace: joe.rice.edu 1043984330 9354 128.42.105.3 (31 Jan 2003 03:38:50 GMT)
X-Complaints-To: abuse AT rice DOT edu
NNTP-Posting-Date: 31 Jan 2003 03:38:50 GMT
X-NewsEditor: ED-1.5.9
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

> > The real filenames are things like
> >         V3P40000.VEC, V3P40001.VEC, ...
> > and we must have been trying to match with the pattern
> >         V3P4*.vec
> > where some of the pattern characters are upper case.
> 
> Why don't they say v3p4*.vec or V3P4*.VEC?

Because years of using DOS/Windows showed no difference in any
other applications?  Yes, you can retrain the users, but it's
not intuitive for them why it should be different.

That's why I believe there should be an option to make it do
the always match behavior.  We could discuss at length which
should be default ... (In particular, this is a minor change in
two places to the setting of variable "caseless" in glob.c).