-
Notifications
You must be signed in to change notification settings - Fork 1.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
Show notification when deactivate command is run in terminal #22121
Comments
microsoft/vscode#145234 could be the long term solution, we can either use it to reliably detect when a We should at least be able to remove part of the workaround which initializes the variables: #22037 (comment). |
Notification:
|
Add wiki for it: https://aka.ms/AAmx2ft |
"deactivate" not working by default is a limitation of our new approach to activate terminals. To fix this the following script needs to be added to any of the init scripts for the shell you're using: Tip: Clicking the Bash
Powershell
Zsh
Fish
Csh
Other shells
Make sure to restart the shell after editing your script, reloading VS Code will not work to apply this change. Why it works:In the new approach, we do not run Alternative solution:Turn off auto-activation: Set |
Output for
|
Bugbash feedback:
|
@brettcannon Your log seems to contain a line:
indicating |
TODO: Add a special variable to indicate whether shell integration is active. |
Thank you! This finally worked to restore the excellent "deactivate" option. Couldn't the new approach to activate terminals be optional? |
All these things should be possible with the new approach as well. If you need more guidance, please create a new issue using |
Thank you. I'll keep using it with the added |
#22448 solves this without the need for a notification or altering |
Ref: #20950
Deactivate command is broken for venv when in
pythonTerminalEnvVarActivation
experiment #22037:Investigate whether it's possible to detect when a "deactivate" command is run and show a notification guiding users to the workaround for their shell: #22037 (comment).
The text was updated successfully, but these errors were encountered: