Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

The token '&&' is not a valid statement separator in this version.

See original GitHub issue

VS Code Version: 1.35.0
OS Version: Windows 10 1903
Code Runner Version: 0.9.10

Describe the bug

PS C:\test> cd "c:\test\" && gcc test.c -o test && "c:\test\"test
At line:1 char:15
+ cd "c:\test\" && gcc test.c -o test && "c:\test\"test
+               ~~
The token '&&' is not a valid statement separator in this version.
At line:1 char:37
+ cd "c:\test\" && gcc test.c -o test && "c:\test\"test
+                                     ~~
The token '&&' is not a valid statement separator in this version.
At line:1 char:40
+ cd "c:\test\" && gcc test.c -o test && "c:\test\"test
+                                        ~~~~~~~~~~
Expressions are only allowed as the first element of a pipeline.
At line:1 char:50
+ cd "c:\test\" && gcc test.c -o test && "c:\test\"test
+                                                  ~~~~
Unexpected token 'test' in expression or statement.
    + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : InvalidEndOfLine
 
PS C:\test>

To Reproduce Steps to reproduce the behavior:

Upgrade VSC from 1.34.0 to 1.35.0.

截图没更改execute map；当然改了也是一样的问题。c、c++、c#都有这个问题，所以与语言无关。

宿主机一直可以复现，1.34.0不存在此问题，更新到1.35.0后出现。

我也在我的win7 x86 vm测试了一下，这个问题本来是有的，覆盖1.34.0再覆盖1.35.0后又消失了。

消失是指会用PS的语法，比如&&会被自动替换为分号，会有$?之类的。