-
Notifications
You must be signed in to change notification settings - Fork 41
Wrong activate button state when using shellStartup #765
Copy link
Copy link
Closed
Labels
area-activationIssue related to activation. Root cause can be from interpreter selection or activation in terminalIssue related to activation. Root cause can be from interpreter selection or activation in terminalarea-terminalEnvironment extension specific terminal issues.Environment extension specific terminal issues.bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug
Metadata
Metadata
Assignees
Labels
area-activationIssue related to activation. Root cause can be from interpreter selection or activation in terminalIssue related to activation. Root cause can be from interpreter selection or activation in terminalarea-terminalEnvironment extension specific terminal issues.Environment extension specific terminal issues.bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bug
When opening a new terminal while having the
shellStartupactivation mode selected, it appears that the state of the activate button isn't updated to reflect that the Python environment was activated. With activation mode set tocommand, you can see in the video below that the button is correctly displaying thedeactivateoption.This is important because not all activation mechanisms are idempotent, e.g. https://pixi.sh/latest/advanced/pixi_shell/.
Screen.Recording.2025-08-26.at.1.45.49.PM.mov