From: pgarceau AT teleport DOT com (Paul Garceau) Subject: (Fwd) bash shell wildcard expansion 4 Feb 1998 02:44:07 -0800 Message-ID: <199802040829.AAA23293.cygnus.gnu-win32@mail1.teleport.com> Reply-To: pgarceau AT teleport DOT com To: gnu-win32 AT cygnus DOT com Greetings, Didn't see any copy of this in the mailing list, so decided to forward it since I know I can't answer the question... ------- Forwarded Message Follows ------- Date: Tue, 3 Feb 1998 01:17:52 -0800 (PST) From: Keith_Graham/Commetrex AT commetrex DOT com I'm using the gnu-win32 tools to give me access to the Unix tools on NT (rather than specifically using the tools to compile Unix code on NT.) As such, having mixed case is not the preferred solution, as has been pointed out in previous discussions. I see where someone posted some patches that appear to change bash's wildcard expansion to support mixed case. As an alternate solution, it appears that it wouldn't be very difficult to put a flag on mount, to make an entire drive be "lower case" only. i.e. any directory read would see entirely lower case entries. This is non-optimal for things like "README", but 99% of the time, I believe it would be the "correct" behavior. And by setting it based on the mountpoint, NFS mounted drives or other mixed case devices would still work. Comments? Would this require any changes out of the winsup directory? Would this cause any problems with any standard tools? Keith Graham skg AT sadr DOT com kgraham AT commetrex DOT com - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help". - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help". Information Systems Consultant NewDawn Productions http://www.teleport.com/~pgarceau/taliesin - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".