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
It would be good if extensions could know whether a new terminal was created by another extension.
The motivating case for this is when using both Python and R. The Python extension sends Python environment activation code to newly created terminals, but if the terminal was created by an R extension this results in a confusing error for the user. I raised this as an issue at the Python extension repo microsoft/vscode-python#11963 but was told that VS Code doesn't provide any way for an extension to know if a terminal was created by another extension microsoft/vscode-python#11963 (comment)
Here is the Python environment activation code that appears in the R terminal, and the R error message that results:
> source /home/[LOCATION]/python-R-test/env/bin/activate
Error: object 'home' not found
Thank you.
The text was updated successfully, but these errors were encountered:
It would be good if extensions could know whether a new terminal was created by another extension.
The motivating case for this is when using both Python and R. The Python extension sends Python environment activation code to newly created terminals, but if the terminal was created by an R extension this results in a confusing error for the user. I raised this as an issue at the Python extension repo microsoft/vscode-python#11963 but was told that VS Code doesn't provide any way for an extension to know if a terminal was created by another extension microsoft/vscode-python#11963 (comment)
Here is the Python environment activation code that appears in the R terminal, and the R error message that results:
Thank you.
The text was updated successfully, but these errors were encountered: