From: "Gary Hubbard" Newsgroups: comp.os.msdos.djgpp Subject: Re: Command line wildcard expansion under Win2K Date: Thu, 30 Jan 2003 12:56:28 -0800 Organization: Sandia National Laboratories, Albuquerque, NM USA Lines: 20 Message-ID: References: <3e394a9a DOT sandmann AT clio DOT rice DOT edu> NNTP-Posting-Host: hubbardpc.ran.sandia.gov X-Trace: sass2141.sandia.gov 1043960152 5538 134.252.7.230 (30 Jan 2003 20:55:52 GMT) X-Complaints-To: usenet AT sass2141 DOT sandia DOT gov NNTP-Posting-Date: Thu, 30 Jan 2003 20:55:52 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Having spent more time looking at this, I am now convinced that things to work as per the man pages, but are still completely counter intuitive to me. 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. I personally see no reason why such a pattern should not work, but clearly there is a lot of logic involved trying to provide UNIX like behavior under MS-DOS and WinXX. Personally, I would prefer all 8.3 filenames returned in lower case, and all others left alone, and for matches to be case insensitive no matter what, but I can see that others might want something else.When I get a chance, I wll make and submit a patch that works the way I prefer, case-insensitive matching everywhere. I will probably not bother changing anything in how filenames are actually returned. Gary