Get environment variable w/o killing CPU on linux #28
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an attempt to fix #20.
I do not have access to a Mac, so I cannot check verify that this change does't re-introduce #4. Although, hacking Travis CI on a different atom package seemed to indicate that
process.env
contained the correct information on the mac environment, but Travis CI also starts Atom from a shell.Ref:
atom.whenShellEnvironmentLoaded()
atom/atom#14164updateProcessEnv
async and addcore:loaded-shell-environment
activation hook atom/atom#13200