You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Automatically activate terminals created by the user when not using the Python command #1387
changed the title [-]Automatically activation terminals created by the user[/-][+]Automatically activate terminals created by the user when not using the Python command[/+]on Apr 13, 2018
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.
Activity
[-]Automatically activation terminals created by the user[/-][+]Automatically activate terminals created by the user when not using the Python command[/+]brettcannon commentedon May 23, 2018
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 commentedon May 23, 2018
Why do we need this
type. Why not just activate it regardless.brettcannon commentedon May 24, 2018
Because Dan Taylor (@qubitron) doesn't like the idea since he uses both Node and Python in the same project 😁
6 remaining items
DonJayamanne commentedon Jun 7, 2018
Tim Arnold (@tiarno), I've tried that myself, and have resorted to manually activating the terminal in the side.
alexwhittemore commentedon Aug 9, 2018
DonJayamanne commentedon Aug 9, 2018
alexwhittemore commentedon Aug 9, 2018
DonJayamanne commentedon Aug 9, 2018
Auto activation of environment in new terminals (#2277)