Subject: Re: bash export problem
From: [email-masked] (Jim Balter)

7 Mar 1997 17:14:04 -0800
Approved: [email-masked]
Distribution: cygnus
Message-ID: <[email-masked]>
References: <[email-masked]>
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 <[email-masked]>
Original-CC: [email-masked]
Original-Sender: [email-masked]

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
"[email-masked]" with one line of text: "help".