This is the mail archive of the cygwin mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
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?
-- PGP/GPG key (ID: 0x9F8A785D) available from wwwkeys.de.pgp.net key-fingerprint 550D F17E B082 A3E9 F913 9E53 3D35 C9BA 9F8A 785D
Attachment:
signature.asc
Description: OpenPGP digital signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |