Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
To: cygwin@cygwin.com
From: Shankar Unni <shankarunni@netscape.net>
Subject: Re: Case handling of environment variables
Date: Sat, 26 Feb 2005 10:52:20 -0800
Lines: 15
Message-ID: <cvqg98$1l1$1@sea.gmane.org>
References: <4220A2CA.7090804@scytek.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041201 Thunderbird/1.0RC1 Mnenhy/0.7
In-Reply-To: <4220A2CA.7090804@scytek.de>
Note-from-DJ: This may be spam

Volker Quetschke wrote:

> Can anyone point me to a message/webpage that explaines the reason
> for this conversion? Unfortunately I didn't find any explanation
> in the archives or the FAQ or the User's Guide.

The biggest reason is PATH. Most (all) POSIX programs will look for the 
environment variable in that specific case, so PATH definitely has to be 
up-cased for Cygwin programs.  The other one is HOME, but that's usually 
synthesized or set explicitly anyway (not like to find an existing 
"Home" environment variable on Windows).

The others shouldn't matter, really - none are really common to Windows 
and POSIX. I guess because there's a *convention* that environment 
variables are declared in uppercase on Unix-y boxes.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/