Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Undocumented execPath placeholder #62231

Closed
fabiospampinato opened this issue Oct 31, 2018 · 4 comments
Closed

Undocumented execPath placeholder #62231

fabiospampinato opened this issue Oct 31, 2018 · 4 comments
Assignees
@weinand
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues

Comments

@fabiospampinato
Copy link
Contributor

We have this thing in the launch configuration of extensions: runtimeExecutable: '${execPath}'.

The execPath placeholder doesn't seem to be documented anywhere.

I assume it points to the current VSC executable, right?
@fabiospampinato fabiospampinato mentioned this issue Oct 31, 2018
Closed
@weinand weinand added the debug Debug viewlet, configurations, breakpoints, adapter issues label Oct 31, 2018
@weinand weinand assigned weinand and unassigned isidorn Oct 31, 2018
@weinand
Copy link
Contributor

weinand commented Jan 10, 2019

yes, correct.
It is an implementation detail of extension debugging.

@weinand weinand closed this as completed Jan 10, 2019
@fabiospampinato
Copy link
Contributor Author

fabiospampinato commented Jan 10, 2019 •
edited
Loading

@weinand I wouldn't call it an implementation detail since all extensions authors are required to create a launch configuration, where execPath must be used, in order to debug their extensions.

@rrd108
Copy link

rrd108 commented Jan 17, 2019

In my case it points to electron instead of vscode executable. There is no information how to change it, or why it is set incorrectly.

@weinand
Copy link
Contributor

weinand commented Jan 17, 2019 •
edited
Loading

If you are running out of source, "execPath" will point to electron.

Very soon it will no longer be necessary to specify a "runtimeExecutable" in an "extensionHost" launch config (and hence no need to use "execPath").

@vscodebot vscodebot bot locked and limited conversation to collaborators Feb 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@weinand weinand

Labels
debug Debug viewlet, configurations, breakpoints, adapter issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@fabiospampinato @weinand @isidorn @rrd108 and others