Automatically activate terminals created by the user when not using the Python command

[DonJayamanne]

microsoft/vscode#46192

This world allow us to automatically activate environments.

Use the following event:

const myTerm = createTerminal();
window.onDidOpenTerminal(t => {
  if (t !== myTerm) {
    // do stuff here
  }
});

[brettcannon]

Without VS Code providing a UI for controlling the "type" of terminal the user wants, having this be opt-out is probably too much when we have a command as-is. If VS Code did add the appropriate UI, though, this would be good.

[DonJayamanne]

Without VS Code providing a UI for controlling the "type" of terminal the user wants

Why do we need this type. Why not just activate it regardless.

[brettcannon]

Because @qubitron doesn't like the idea since he uses both Node and Python in the same project 😁

[qubitron]

I was extrapolating from my own experience that a polyglot developer that only uses Python for a part of their app would be annoyed that we always activate Python in the terminal and we don't have an easy way to say "create me a terminal without python". At the same time, many people have asked to automatically activate Python in the terminal (or are confused when it doesn't happen).

Thinking more about it... more would probably benefit from a default activated terminal than would be annoyed, so it's probably better tradeoff to type "deactivate" when you don't want the activated python terminal. In case it really disrupts people's workflows or causes issues, we can add an option to disable the feature and they can fall back to using the "Python: Create Terminal" command.

[brettcannon]

Labels changed to reflect the new thinking.

[tiarno]

I was looking for a way to open two Python terminals side by side. I think the default activated terminal would work for that, so +1.

[DonJayamanne]

@tiarno, I've tried that myself, and have resorted to manually activating the terminal in the side.