Re: bash export problem

[Fergus Henderson <fjh at cs dot mu dot OZ dot AU>]

Christoph Kukulies, you 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? 

Here's what the source code says (this is from `src/winsup/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. */

I think a case-insensitive getenv() would be better.
The current approach breaks all code using lower-case environment
variables to communicate between processes, whereas a case-insensitive
getenv() would only break code that used both upper and lower case
versions of the same name.

-- 
Fergus Henderson <fjh@cs.mu.oz.au>   |  "I have always known that the pursuit
WWW: <http://www.cs.mu.oz.au/~fjh>   |  of excellence is a lethal habit"
PGP: finger fjh@128.250.37.3         |     -- the last words of T. S. Garp.
-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".