Re: PATH vs. Path ([Fwd: Returned mail: see transcript for details]

[Alessandro Vesely]

Eli Zaretskii wrote:
>
> > Thus, it looks like `Path' is needed to avoid _contaminating_ the Windows
> > setup with unixy stuff.
> 
> I don't understand.  Didn't somebody (you?) say that Windows
> environment is case-insensitive, and that the standard C library
> function `getenv' will find both Path and PATH?  If so, it sounds like
> exporting just PATH to the subsidiary programs will do, as both Bash
> and other Windows programs will be happy.  Am I missing something?

I agree. I found an interesting post in the uwin mailing list:
| http://www.research.att.com/lists/uwin-users/1998/09/msg00075.html
| To: address@hidden 
| Subject: PATH philosophy? 
| From: Luke Kendall <address@hidden> 
| Date: Thu, 17 Sep 98 16:02:59 +1000 
| 
| ...
| A simple safe rule is to always use upper case for variables.

> > I don't include the brutal patch, because it's brutal.
> 
> What does it do? push only PATH into the environment?  If so, I think
> it's what we need.

In main.c there is some logic about how PATH was spelled in the current
environment. That part should be simplified. In variable.c it is enough
to change "Path" to "PATH". I'll try and submit a patch later.