Mail Archives: cygwin-developers/1999/06/07/16:17:10
Ok. You finally forced me to check the code.
Environment variables are uppercased in the first invocation of
a cygwin process but subsequent children of that process do not
do this. So, if you've used mixed case in environment variables prior
to running BASH the mixed case will not show up in "env" output:
c:\>set cArol=This is Carol
bash-2.02$ env | grep cArol
bash-2.02$ export Bobby="This is Bobby"
bash-2.02$ env | grep "Bobby"
Bobby=This is Bobby
As far as suggesting something; this is open source. If you would like
to submit a patch please feel free to do so. Otherwise, I have no plans
on scheduling time to implement this behavior.
On Mon, Jun 07, 1999 at 04:01:30PM -0400, Thomas, Mike wrote:
>Ok it is still the same as in b18, this breaks us, we rely on environment
>variables to remain in the case they began in.
>Is this something we can suggest in some way to be added in a future rev?
>PS I've been on this mailing list and quite since just after b18 :)
> Mainly because we are still using a heavily modified b18, mostly bug
> fixes that have been addressed in b20, except the environment..
>From: Chris Faylor [mailto:cgf AT cygnus DOT com]
>Sent: Monday, June 07, 1999 1:19 PM
>To: Thomas, Mike
>Cc: cygwin-developers AT sourceware DOT cygnus DOT com
>Subject: Re: Environment Variables
>On Mon, Jun 07, 1999 at 01:08:42PM -0400, Thomas, Mike wrote:
>>I have a quick question... In b18 environment variables were being changed
>>to uppercase before a executing a new process. In b20 is this still the
>>case? If so is there a mechinisim by which we can change this to not alter
>>the environment Maybe a registry entry?
>I don't know the answer off the top of my head. The actual code
>involved is is in environ.cc. I'd suggest that you look there and write
>some simple test cases to supply your own answer.
- Raw text -