-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix for spawning bufferedNodeProcess #21
Comments
Doesn't BufferedNodeProcess do this already? https://github.com/atom/atom/blob/master/src/buffered-node-process.coffee#L49 |
Yeah you are right. The problem is the default options.env. Using process.env doesn't work and when I set the env myself it doesn't do this line of code. https://github.com/atom/atom/blob/master/src/buffered-node-process.coffee#L48. I'm currently going through each property on process.env and seeing which one is causing the problem and I'll report back when I figure that out |
Yep, specifying a custom env object makes it work, but then the |
Why does it break the |
'cause |
I just tested adding HOMEDRIVE and HOMEDIR to the options.env from process.env and the code still works on windows. For a temporary fix, we could have windows specific code that creates an options object with just those properties. However, it would be ideal if we could figure out which exact property is causing things to fail. |
I am like super-stretched up between work and I would highly appreciate it if someone narrows the error down to a single env var. |
Fixed by #22 |
@steelbrain
I fixed the problem in AtomLinter/linter-jshint#151. You need to have an options object and pass it into bufferedNodeProcess :
I can create a PR for the atom-linter code if you would like.
The text was updated successfully, but these errors were encountered: