Skip to content

Conversation

@vadimcn
Copy link
Contributor

@vadimcn vadimcn commented Sep 14, 2014

Closes #16937

@brson
Copy link
Contributor

brson commented Sep 15, 2014

Can you mention in the docs for Command that the environment variable is case-insensitive, and whether it gets turned into upper- or lower-case?

Also, if we're going to do this for Command should we also do something similar for os::setenv and os::getenv?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could these stay private to this module?

@vadimcn
Copy link
Contributor Author

vadimcn commented Sep 16, 2014

Updated.
getenv()/setenv() already handle case correctly, because they just defer to the OS API..

@vadimcn
Copy link
Contributor Author

vadimcn commented Sep 17, 2014

Rebased. r?

@vadimcn
Copy link
Contributor Author

vadimcn commented Sep 18, 2014

re-r?

bors added a commit that referenced this pull request Sep 18, 2014
bors added a commit that referenced this pull request Sep 18, 2014
@bors bors closed this Sep 18, 2014
@bors bors merged commit 8b84911 into rust-lang:master Sep 18, 2014
@vadimcn vadimcn deleted the env-keys branch March 1, 2015 08:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Windows: process::Command::env should be case-insensitive

5 participants