-
Notifications
You must be signed in to change notification settings - Fork 29.2k
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
EnvironmentVariableCollection.description only works for one extension #186859
Comments
Fixed in main #186861 |
Thanks for taking care of it while I was out! Can this be closed? |
@karrtikr this one's going into the recovery build, didn't quite make the cut for 1.80.0. |
@karrtikr verified that JavaScript debug terminals are getting the expected env - can you pls lmk what the repro steps were here? |
You can add the following setting to activate description for Python ext: After which, if you select a virtual environment (Python: Select Interpreter), it should use env collection to activate terminal with appropriate description, something like: Description is the "Enable Nodejs..." string next to "Javascript debugger:", it appears when hovering over the terminal label. |
Seems to work 👍 |
This is the reason js-debug isn't working but git is:
vscode/src/vs/platform/terminal/common/environmentVariableCollection.ts
Lines 139 to 161 in 01d4949
This is probably a good candidate for recovery, not a good reason to push 1.80.0 out though.
The text was updated successfully, but these errors were encountered: