-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Specify terminal profile to use for Python terminal #21730
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 7 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue. |
I 👍 upvote!I have 2 terminal profiles: custom 'tmux' for keeping session and default 'bash'. I would like to only active venv in 'bash' (default behavior), but not in 'tmux'. |
Thank you for submitting your feature request and everyone who considered it! Unfortunately, this issue did not receive enough votes over the allotted time, and so we are closing the issue. |
Request
I am requesting two new settings that can either work separately or together:
python.terminal.profile
python.terminal.activateEnvInTerminals
I would like to point the "Python terminal" to a specific integrated profile. Currently, the Python terminal always points to the default terminal specified by e.g.
terminal.integrated.defaultProfile.windows
setting. It would be great if users could point it to a particular terminal profile, via a setting likepython.terminal.profile
that accepts a terminal profile name (in exactly the same way thatterminal.integrated.defaultProfile.windows
does). I could see this new setting also being a list or dictionary with entries for Windows, OSX, and Linux.I would also like more flexibility in choosing which terminals attempt to automatically activate a Python environment. Currently, we have the choice to auto-activate environments in the current terminal via
python.terminal.activateEnvInCurrentTerminal
and in all terminals viapython.terminal.activateEnvironment
. I would like to see a new setting likepython.terminal.activateEnvInTerminals
that accepts a list of named terminal profiles.Current workaround
Set
terminal.integrated.defaultProfile.windows
to a custom profile andpython.terminal.activateEnvironment
to True in the workspace settings.Background
I am experimenting with ways to separate Conda environment activation from the standard Powershell terminal. My current solution is to create a "Conda" terminal like so:
which allows me to add Conda functionality to the terminal. When combined with the
"python.terminal.activateEnvironment"
setting, it also activates the specific environment associated with the project. However, given the currently available settings I cannot launch this custom environment via the "Python: Create Terminal" command, nor can I activate the environment automatically unless I setpython.terminal.activateEnvironment
toTrue
.Related issues: #20562, #2559, #21864
The text was updated successfully, but these errors were encountered: