[Bug][VS Code 1.56] Not detect shell on Windows correctly

[officer]

• VS Code Version: 1.56.0
• OS Version: Windows_NT x64 10.0 19042
• Code Runner Version: v0.11.3

Describe the bug
When we assign "Command Prompt" to "terminal.integrated.defaultProfile.windows" parameter, "&&" in code-runner.executorMap will be translated into "; if ($?) { } style which is not working on Command Prompt.

To Reproduce
Steps to reproduce the behavior:

1. Configure "terminal.integrated.defaultProfile.windows": "Command Prompt" in settings.json
2. Include "&&" in any of language "code-runner.executorMap".
3. Run the code.

Actual behavior
Translate "&& " into "; if ($?) { }"

Expected behavior
Interpret "&&" as is.

Screenshots
If applicable, add screenshots to help explain your problem.

[officer]

Probably it's a visual studio code side issue, but anyway I post it at here now.

[blackpancake]

I also found this problem. However, I found a temporary solution to this problem:

add "terminal.integrated.shell.windows": "C:\\Windows\\System32\\cmd.exe" in settings.json to make CodeRunner not translate & into ; if ($?) { }.

However, this will cause a warning in settings.json. I guess this may be because CodeRunner doesn't realize that vscode has abandoned the "terminal.integrated.shell.windows" setting.

[formulahendry]

Related issues:

• Shell type is detected incorrectly after VSCode update microsoft/vscode-python#16175
• If terminal.integrated.shell doesn't have a matching terminal.integrated.profiles entry the shell path will be ' ' microsoft/vscode#121760

[formulahendry]

@officer @blackpancake This issue has been fixed. Please install the latest version and have a try.

[jack20951948]

still have issue with bash....

[blackpancake]

still have issue with bash....

In CMD, this issue has been fixed.

[formulahendry]

@jack20951948 You could use below setting:

"code-runner.terminalRoot": "/"

[jack20951948]

@jack20951948 You could use below setting:

"code-runner.terminalRoot": "/"

yeah...I've already had this setting...

[jack20951948]

seems in git bash still have some issues