From: Charles Sandmann Newsgroups: comp.os.msdos.djgpp Subject: Re: Command line wildcard expansion under Win2K Date: Thu, 30 Jan 2003 09:54:02 CST Organization: Rice University, Houston TX Lines: 35 Message-ID: <3e394a9a.sandmann@clio.rice.edu> References: NNTP-Posting-Host: clio.rice.edu X-Trace: joe.rice.edu 1043943611 9637 128.42.105.3 (30 Jan 2003 16:20:11 GMT) X-Complaints-To: abuse AT rice DOT edu NNTP-Posting-Date: 30 Jan 2003 16:20:11 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 > > 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? Okay, lets go back to my examples: "A.vec" exists (A upper case): C:\>djecho a*.vec A*.vec A*.VEC a*.VEC a.vec A.vec A*.VEC a*.VEC (current behavior) a.vec A.vec A.vec a.vec (intuitive behavior) In other words, act as if you had passed these strings to the "dir" command. "B.VEC" exists (all upper case): C:\>djecho b*.vec B*.vec b*.VEC B*.VEC b.VEC B*.vec b*.VEC B.VEC (current behavior) b.vec b.vec b.vec B.VEC (intuitive behavior) In other words, I think forcing an exact match on any upper case characters is not intuitive - that all matches should be case insensitive - at least as an option. The case of what is returned above is not important - but the fact that it finds a match. > > 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? I think this behavior should be decoupled from FNCASE.