Fix #532: DEVPATH env variable not being set for integrated console #570
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… console This change adds a workaround for setting the DEVPATH environment variable when launching the language server inside of the integrated terminal UI. This environment variable needs to be set for Windows PowerShell development builds but it currently can't because there's no API parameter for passing along environment variables. The workaround is to generate a batch script which can set the environment variable before launching PowerShell.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 change adds a workaround for setting the DEVPATH environment variable
when launching the language server inside of the integrated terminal UI.
This environment variable needs to be set for Windows PowerShell
development builds but it currently can't because there's no API parameter
for passing along environment variables. The workaround is to generate a
batch script which can set the environment variable before launching
PowerShell.