Auto-env activation provides a poor out-of-the-box experience with PS1 (KeyboardInterrupt race)

[Mattwmaster58]

It was briefly mentioned here: #1011, but I don't think it's fixed, only a workaround was provided.

To summarize, with auto-env activation + running from the top right corner there's a race condition: if your python script doesn't get done in about a half second, (presumably) this extension KeyboardInterrupts to run the PS1 activation script. Here's what it looks like:

WindowsSandboxRemoteSession_AZXCAznRcA.mp4

There was a workaround provided was to set a config value, but I think the UX should be better than that. Especially because the issue (for me) was racey. So for the first however many months, I just ran the script again and hoped that it wouldn't happen this time. Actually come to think of it was probably re-using the activated terminal avoiding the need to run the activation script.

I assume there's something from us setting the default "python-envs.terminal.autoActivationType" to "shellStartup" (which avoids this issue)?

[anthonykim1]

@Mattwmaster58 The plan is to set the auto activation type to shellStartup as default. Once env extension rolls out 100%, we would only then start rolling out shellStartup as default.

#640 has been resolved. Please try out the latest pre-release of env extension and also latest insider version of vscode.

You're likely on release version of env ext and stable version of vscode atm.

Insiders build