From: tomas DOT fasth AT twinspot DOT net (Tomas Fasth)
Subject: Re: Question about bash and case sensitive exports
23 Nov 1997 22:27:14 -0800
Message-ID: <34789F70.F24A80BF.cygnus.gnu-win32@twinspot.net>
References: <2 DOT 2 DOT 32 DOT 19971123192213 DOT 00963010 AT ma DOT ultranet DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: gnu-win32 <gnu-win32 AT cygnus DOT com>

I got a hint that a possible DOS compatibility fix in cygwin.dll is the
cause for my problem. Am I the only one experiencing problems because of
this minor (POSIX?) incompatibility?
Does lower-case variable names in the DOS environment break existing DOS
programs? I'm not very happy with a situation were ancient DOS
restrictions is overruling compatibility with an environment which
cygwin32 are suppose to emulate in an as seamless as possible manner
(i.e. Unix).

I might look deeper into a possible solution. A good compromise seem to
be if compatibility with both environments could be uphold. I have an
idea of keeping record of non-DOS variables separately and provide them
when asked for by programs linked with cygwin.dll.

Is this something the gnu-win32 community want to have fixed?

Tomas
-
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".