-
Notifications
You must be signed in to change notification settings - Fork 27.9k
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
Use path_helper in user shell in darwin #29864
Conversation
Managed to work around the build issues with NPM5 and get a copy of this branch running via The flowtype extension executes without complaint and without needing to launch vscode from inside a terminal whose CWD is the project directory. I manually instrumented the flowtype extension here to log the However, this is still an instance of vscode launched from inside a terminal. I wracked my brains trying to figure out how to produce a double-clickable build from the instructions to no avail. Attempting to drop various promising-looking files on the DnD target didn't yield anything (various files in Any pointers on how to test this effectively? |
@idan If you'd like to run this build, just download it. |
cc @idan @NinoFloris |
Same here
…On Thu, Aug 17, 2017, 19:54 Nino Floris ***@***.***> wrote:
Doing a process.env in this build shows me it actually did not run? still
just path defaults
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#29864 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABYw460t95uuukwNPWVQ9IxCuisLr-Vks5sZH5KgaJpZM4OJaLh>
.
|
That is odd @NinoFloris, as Code should be running |
it should as running path_helper from within fish shell returns a lot of info. I might be thick but how does getDarwinEnvironment actually return an environment from that func? |
It doesn't launch |
OK, so I looked at how atom is handling this, and it looks like it's the same sort of setup. After some experimentation, it seems that the wiring of stdout is busted. When I try running (() => {
const cp = require('child_process')
const buffers = []
const child = cp.spawn(process.env.SHELL, ['-lc', 'command /usr/libexec/path_helper'], {encoding: 'utf8', detached: true, stdio: 'pipe'})
child.on('error', (e) => {
console.error(e)
})
child.stdout.on('data', (data) => {
buffers.push(data)
})
child.on('close', (code, signal) => {
console.log(Buffer.concat(buffers).toString('utf8'))
})
})(); The above results in output (redacted) like:
I know that originally this used a stdio setup like If invoked with -i, it produces the same output, but prefixed with a block like:
Not sure how this affects other shells yet; but at least it's showing the correct value for me, which is progress. Maybe it's a good clue on how to proceed? |
The use of |
https://askubuntu.com/questions/512770/what-is-use-of-command-command If you remove |
Yes, using |
Looks good in 1.19! 😍 |
Awesome sauce. |
Fixes #21655