This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: CMD, case-insensitive file-name completion
- To: RPraetorius at AspenRes dot Com
- Subject: Re: CMD, case-insensitive file-name completion
- From: Michael Condict <condict at opengroup dot org>
- Date: Thu, 29 May 1997 10:22:56 -0400
- cc: Scott dot Mintz at po dot cle dot ab dot com (Scott Mintz), gnu-win32 at cygnus dot com, condict at opengroup dot org
In message <B0000119176@mx1.aspenres.com>, you write:
> CMD also has case-insensitive filename completion.
I'd also like to note, if we're using other Windows command processors
as a precedent, that all of the following command processors have
case-insensitive filename completion, and also have case-insensitive
file-name pattern matching (i.e. "a*" matches both "abc" and "Alpha"):
- NT command processor
- 4DOS for NT
- MKS UNIX Toolkit Korn Shell
Moreover, all of these command processors correct the case as you
type the completion character, just like my proposed changes to bash.
So bash currently stands alone in not being case-insensitive. I'd say
that's more surprising behavior, on a Windows system, than the fact
that UNIX users expect case-sensitivity.
And while were on the topic of file globbing, can someone please tell
me why there are at least three slightly different copies of glob.c
spread throughout the source tree? I've modified the one in the bash
source tree to do case-insensitivity, but this won't help the find
command, for example, and whatever other programs have built-in file-
name matching.
Michael Condict m.condict@opengroup.org
The Open Group Research Inst. (617) 621-7349
11 Cambridge Center
Cambridge, MA 02142
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".