-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Task property "presentation": {"reveal": "never"} is not working when Python extension is active #3852
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
Issue moved to Microsoft/vscode #66056 via ZenHub |
@DonJayamanne could you have a look at #65179 before we close this one on our repo. It would seem that the integrated terminal only opens when the Python extension is active... |
Hello, It was me who opened issue #65179 at vscode, but because it only occurs when using the Python extension, I closed it and opened a new issue here. Thanks, JM |
Yes, I didn't realize that bit when I closed it! Thanks, we will have a look and see if there is something we are doing on our end. |
Please add the following setting |
Hello, I'm sorry but that makes no sense. I want the terminal to activate the venv. What should not happen is the task to show in terminal if the option
is present. And this only happens with the Python extension activated. Thanks, JM |
Uh oh!
There was an error while loading. Please reload this page.
Environment data
Expected behaviour
Task property "presentation": {"reveal": "never"} should never show the terminal panel when the task runs.
Actual behaviour
Task property "presentation": {"reveal": "never"} always shows the terminal panel when the task runs and the Python extension is active.
Steps to reproduce:
Output in terminal (that should not appear)
I created a simple Task and added the presentation item, hoping that that would allow me to never show the integrated terminal (as it is reported in the doc at
https://code.visualstudio.com/docs/editor/tasks#vscode
but it isn't working. It always shows the integrated terminal.
Thanks,
JM
The text was updated successfully, but these errors were encountered: