Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <4220A2CA.7090804@scytek.de>
Date: Sat, 26 Feb 2005 11:24:42 -0500
From: Volker Quetschke <quetschke AT scytek DOT de>
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Case handling of environment variables
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigA093448305333B5E70399259"

--------------enigA093448305333B5E70399259
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

When you search the archives you find a few messages stating that
windows environment variables get converted to upper case. There
was even a patch by Ernie Coskrey discussing a new option controlling
this behavior on cygwin-patches.

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.

I'm guessing here: Is the reason for this behavior that cygwin programs
can use upper/lower/mixed case simultaneously
(In bash:
$ export a=1; export A=2; echo $a $A
1 2
)
and windows cmd.exe cannot?

Volker

-- 
PGP/GPG key  (ID: 0x9F8A785D)  available  from  wwwkeys.de.pgp.net
key-fingerprint 550D F17E B082 A3E9 F913  9E53 3D35 C9BA 9F8A 785D

--------------enigA093448305333B5E70399259
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCIKLKPTXJup+KeF0RAkSyAJ43nsQbhhgRzLRoRrrUE6mKl2Af6wCaAtA1
4OCW0qir/GOJps9tuHR6KXY=
=//Fy
-----END PGP SIGNATURE-----

--------------enigA093448305333B5E70399259--