From: fjh AT cs DOT mu DOT OZ DOT AU (Fergus Henderson)
Subject: Re: Case sensitivity in filenames
5 Jan 1999 11:18:18 -0800
Message-ID: <19990105231647.23310.cygnus.gnu-win32@mundook.cs.mu.OZ.AU>
References: <c=UK%a=_%p=Origin-it%l=UKRUX002-990104143425Z-45787 AT ukrax001 DOT ras DOT uk DOT origin-it DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: Geoffrey Noer <noer AT cygnus DOT com>
Cc: "Moore, Paul" <Paul DOT Moore AT uk DOT origin-it DOT com>,
        "'Larry Hall'" <lhall AT rfk DOT com>, "'Gnu Win32'" <gnu-win32 AT cygnus DOT com>

On 04-Jan-1999, Geoffrey Noer <noer AT cygnus DOT com> wrote:
> On Mon, Jan 04, 1999 at 02:34:25PM -0000, Moore, Paul wrote:
> [...]
> > Unfortunately, I'm not willing to limit myself to bash...
> > 
> > Paul.
> 
> Could you explain at greater length what you want Cygwin to do
> w.r.t. case insensitivity?

If a program is invoked directly from the DOS command line, or from a
non-cygwin program, then I think wildcards still get expanded.
In this case, it is the cygwin startup files (crt0.o or whatever)
rather than bash which is doing this glob expansion.

There should be some setting for the CYGWIN environment variable, or
perhaps a different environment variable, which controls whether this
globbing is case sensitive or not.  Ideally there should be also be a
gcc link option which controls the default behaviour in case the
environment variable is not set.

In addition, bash and readline should also support optional 
case insensitivity for filename globbing and filename completion.

-- 
Fergus Henderson <fjh AT cs DOT mu DOT oz DOT au>  |  "Binaries may die
WWW: <http://www.cs.mu.oz.au/~fjh>  |   but source code lives forever"
PGP: finger fjh AT 128 DOT 250 DOT 37 DOT 3        |     -- leaked Microsoft memo.
-
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".