Open Spitfire1900 opened 8 months ago
Thanks for reporting @Spitfire1900 . Please let me know if I'm understanding correctly. As I understand this, you're reporting 2 issues.
First, you have terminal.integrated.automationProfile.windows
set but not terminal.integrated.defaultProfile.windows
. The extension reads the latter and ignores the former, causing issues. Second, once you set defaultProfile
you get the error shown.
Is that accurate or am misunderstanding?
That is correct.
terminal.integrated.defaultProfile.windows
set to a custom Xonsh profile.terminal.integrated.automationProfile.windows
set to:
"terminal.integrated.automationProfile.windows": {
"path": "C:\\Windows\\System32\\cmd.exe",
"icon": "terminal-cmd"
}
terminal.integrated.defaultProfile.windows
instead of terminal.integrated.automationProfile.windows
.terminal.integrated.automationProfile.windows
instead of terminal.integrated.defaultProfile.windows
would resolve this issue.Great. Thanks for confirming @Spitfire1900 .
I use Xonsh on Windows and unless I set
"terminal.integrated.defaultProfile.windows": "Command Prompt"
(or Powershell) the program behaves as if it is on Linux, however this causes a The specified path is invalid.