From: jqb AT netcom DOT com (Jim Balter)
Subject: Re: bash export problem
7 Mar 1997 17:14:04 -0800
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <331FE657.3907.cygnus.gnu-win32@netcom.com>
References: <199703070816 DOT JAA13924 AT gilberto DOT physik DOT rwth-aachen DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.01Gold (WinNT; I)
Original-To: Christoph Kukulies <kuku AT gilberto DOT physik DOT rwth-aachen DOT de>
Original-CC: gnu-win32 AT cygnus DOT com
Original-Sender: owner-gnu-win32 AT cygnus DOT com

Christoph Kukulies wrote:
> 
> > Christoph Kukulies wrote:
> >
> > > The escape strings are not exported to the environment, i.e., they are
> > > empty.
> >
> > cygwin upcases all environment names.
> 
> Huh? Is this a DOS resp. NT mandate?

Huh huh?  The cygwin code is riddled with hacks, bugs, and
misunderstandings; this is just another one.  Here's the relevant
comment from dcrt0.cc:

/* Amazingly, NT has a case sensitive environment name list,
   only sometimes.
   eg, it's normal to have NT set your "Path" to something.
   Later, you set "PATH" to something else.  This alters "Path".
   But if you try and do a naive getenv on "PATH" you'll get nothing. 
   
   So we upper case the labels here to prevent confusion later. */

You have the code and thre right to change it.  Have at it.

--
<J Q B>
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".