Prerequisites

• Can you reproduce the problem in safe mode?
• Are you running the latest version of Atom?
• Did you check the debugging guide?
• Did you check the FAQs on Discuss?
• Are you reporting to the correct repository?
• Did you perform a cursory search to see if your bug or enhancement is already reported?

For more information on how to write a good bug report or enhancement request, see the CONTRIBUTING guide.

Description

On Windows, environment variable names are case-insensitive.

In Atom 1.7.0 for Windows, process.env.PATH is returning undefined if the path environment variable is defined as Path (it is then accessible as process.env.Path only).

In 1.6 the environment variable is accessible as both PATH and Path.

Steps to Reproduce

1. On Windows, ensure your path environment variable (%PATH%) is defined as Path (not PATH as is customary on UNIX).
2. Launch Atom and open the dev console (ctrl+alt+I)
3. Evaluate process.env.PATH.

Expected behavior: process.env.PATH should return the contents of the Path environment variable, regardless of what case its name is spelled in (as in Atom 1.6).

Actual behavior: process.env.PATH evaluates to undefined. Only process.env.Path returns the proper contents of the environment variable.

Versions

Atom : 1.7.0-beta0
Electron: 0.36.8
Chrome : 47.0.2526.110
Node : 5.1.1