Should there be an indication that python has been activated for the terminal?

[meganrogge]

Testing #340

There's no UX indicating which terminals have been activated, which then causes me to have some confusion when I have bash, zsh, fish and pwsh terminals open, change the setting, and it only suggests doing this for bash.

[eleanorjboyd]

@karthiknadig I wonder on this one too- any ideas on what this could look like to make it more obvious?

cc @anthonykim1

[anthonykim1]

Actually the experience we want to head towards with the golden scenario activation is "activation just working right off the bat", meaning environment extension will contribute the appropriate activation command and core will use that to activate, with shellStartup respectively given shell integration is active.

So what we want to see is terminal being activated automatically when people open their terminal (without having to see these activation commands, nor the notification prompt above) and provide activated terminal ready to go -> whether it is for user or copilot.

Easiest giveaway will be the (.venv) prompt or equivalent in different types of them, or simple which python should work as well.

Also good thing to remember is that with shell startup migrated to shell integration and running from core, people will see way less of these notification. Seeing these prompts will be way less now and will pretty much only happen when shell integration is not available/disabled.

FYI you will see the prompt for cmd prompt since we only have shell integration scripts for pwsh, zsh, bash, and fish in core currently.

I think we already have some kind of icon coming from environment extension that says activate or deactivate, but I'd be much happier WITHOUT more UI, since prompt additions like (.venv) or commands which python are enough giveaway.

[eleanorjboyd]

@anthonykim1 ill let you decide here if you think this should be kept open or closed as we are moving in this different direction with the golden scenario

[anthonykim1]

We should be good to close this, with (.venv) showing up and extra icon that allow user to deactivate/activate.
Aiming to show way less of the permission modal dialog too. #1023