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
Running code using the "Run Python File in Terminal" icon should support shells outside of pwsh, cmd, etc. If using Powershell, the command is prefixed with &. If using CMD, the command is not prefixed. If using another shell (such as nushell), the command is still prefixed as if it was powershell. This causes the command to fail.
I have been using the setting "terminal.integrated.shell.windows" for setting the shell to utilize.
The text was updated successfully, but these errors were encountered:
Thank you for the suggestion! We have marked this issue as "needs decision" to make sure we have a conversation about your idea. We plan to leave this feature request open for at least a month to see how many 👍 votes the opening comment gets to help us make our decision.
Hey @kfardanesh! If we were to do it, I believe we'd address #11812 so that it's possible to configure the shell for running Python files. So I'm closing in favour of that 😊
Running code using the "Run Python File in Terminal" icon should support shells outside of pwsh, cmd, etc. If using Powershell, the command is prefixed with
![image](https://user-images.githubusercontent.com/12469063/80520821-fabbe780-8957-11ea-9fed-1c5e6f42c4a6.png)
&
. If using CMD, the command is not prefixed. If using another shell (such as nushell), the command is still prefixed as if it was powershell. This causes the command to fail.I have been using the setting
"terminal.integrated.shell.windows"
for setting the shell to utilize.The text was updated successfully, but these errors were encountered: