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

imba-tjd · 2019-06-06T08:19:16Z

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的语法，比如&&会被自动替换为分号，会有$?之类的。

The text was updated successfully, but these errors were encountered:

imba-tjd · 2019-06-06T08:53:59Z

Workaround: add "terminal.integrated.shell.windows": "powershell.exe" to settings

This is a VSC's feature... See microsoft/vscode-cpptools#3718 (comment)

pieandcakes · 2019-06-06T17:24:49Z

@imba-tjd that is not the right place to link it. We at the the CppTools extension don't have anything to do with VS Code's features. Please file/link issues to their repo at https://github.com/microsoft/vscode/issues

imba-tjd · 2019-06-06T21:42:12Z

@pieandcakes I know, but I just want the notice and that 2 more links which Tyriar mentioned. 😄

pieandcakes · 2019-06-06T23:32:51Z

Can you update your link to: microsoft/vscode-cpptools#3718 (comment) so its the specific comment?

imba-tjd · 2019-06-06T23:35:59Z

🆗

xiachangsong · 2019-06-07T13:57:27Z

I'm weak. I still don't know how to solve this problem.

formulahendry · 2019-06-07T14:50:34Z

@xia1065 please refer to https://code.visualstudio.com/docs/editor/integrated-terminal#_configuration

formulahendry · 2019-06-07T23:17:25Z

Let's see whether microsoft/vscode#75091 would be useful

xiachangsong · 2019-06-08T01:33:02Z

Thank you. I've settled it. The problem was solved by clicking on "Select the default shell" in "Terminal".

formulahendry · 2019-06-12T13:06:40Z

Have a workaround fix for this issue.
Waiting for VS Code API for a better resolution.

rohan2017 · 2019-10-13T20:36:09Z

I am having the same issue right now. How exactly did you fix it

jesusarockias · 2019-10-16T10:07:16Z

I am having the same issue right now. How exactly did you fix it

xiachangsong · 2019-10-16T10:16:55Z

I remember adjusting that PowerShell in my  circle.emm..  you can have try to change optiona.

…

---Original--- From: "jesusarockias"<notifications@github.com> Date: Wed, Oct 16, 2019 18:07 PM To: "formulahendry/vscode-code-runner"<vscode-code-runner@noreply.github.com>; Cc: "xiachangsong"<1065256104@qq.com>;"Mention"<mention@noreply.github.com>; Subject: Re: [formulahendry/vscode-code-runner] The token '&&' is not a valid statement separator in this version. (#491) I am having the same issue right now. How exactly did you fix it — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

imba-tjd · 2019-10-16T10:41:24Z

For now you don't need to change anything. So you two probably not have the same issue as this one.

But you can always use the "shell-specific" command.

NguyenManhCam404 · 2020-02-06T10:08:04Z

You just need to change "&&" to ";"

mikr13 · 2020-05-01T16:01:14Z

You just need to change "&&" to ";"

Yeah but that doesn't solve the problem if an npm package calls that command, right?
For ex.: husky postinstall:- husky@4.2.5 postinstall: "opencollective-postinstall || exit 0"

Raag007 · 2020-06-01T02:46:06Z

Running this npm config set script-shell command should fix 'The token '&&' is not a valid statement separator in this version" problem.

-Raag!

awantea106 · 2020-12-14T07:31:02Z

You must use CMD default Windows. cant with VSC or GIT bash

proggdeath · 2021-01-19T02:36:42Z

You just need to change "&&" to ";"

This solve my problem.
Thanks a lot ! 👯‍♂️

Satyajit517 · 2021-02-13T09:45:31Z

You just need to change "&&" to ";"

But where should i change it please tell me i am now in this

Chruftl · 2021-02-18T01:38:46Z

Tested for Windows 7 / Visual Studio Code version 1.53.2

Search in the following directory for a file "package.json":
C:\Users\Name_of_your_Computer\.vscode\extensions\formulahendry.code-runner-0.11.2
-> first make a copy of the file!
Edit this file using Visual Studio Code. (-> copy the directory path from the Windows-Explorer to the "Open File" )
Go to Line 129, 130 and 131 (about) and change the entries to somthing like that:
( replace all "&&" by ";" - set additional the path ; - remove $dir(before$fileNameWithoutExt) for the last call - and set "artificial" double quotes "...." by \" and .... \" - add & .\ in front of the Filename [ & ".\Filename"] ) :

-> The $dir$fileNameWithoutExt command doesn't work properly! Double quotes ("...") are placed wrong.

"c": "cd $dir ; gcc $fileName -o $fileNameWithoutExt ; $Env:PATH += $dir ; & \".\\$fileNameWithoutExt\"",
"cpp": "cd $dir ; g++ $fileName -o $fileNameWithoutExt ; $Env:PATH += $dir ; & \".\\$fileNameWithoutExt\"",
"objective-c": "cd $dir ; gcc -framework Cocoa $fileName -o $fileNameWithoutExt ;$Env:PATH += $dir ; & \".\\$fileNameWithoutExt\"",

Close and restart the program twice (really!! / do it / don't think about).

Result of the output:
Windows PowerShell
Copyright (C) 2009 Microsoft Corporation. Alle Rechte vorbehalten.

PS C:\my_Visual_Studio_Code> cd "c:\my_Visual_Studio_Code\5_hello_CPP" ; g++ 5_helloworld.cpp -o 5_helloworld ; $Env:PATH += "c:\my_Visual_Studio_Code\5_hello_CPP" ; & ".\5_helloworld"
- hello world -
PS C:\my_Visual_Studio_Code\5_hello_CPP>

sbccas · 2021-02-19T16:17:43Z

Worked for me too . Thanks a lot

hiteshkumawatpro · 2021-02-22T18:50:00Z

This problem can be fixed by following few steps:

Open Terminal
Select----SELECT DEFAULT SHELL---option provided in menu list type option on the right-hand side.
Select -- COMMAND PROMPT---CMD.EXE

then run the code again and enjoy.

SahilKesarwani · 2021-04-17T15:20:50Z

Tested for Windows 7 / Visual Studio Code version 1.53.2

Search in the following directory for a file "package.json":
C:\Users\Name_of_your_Computer.vscode\extensions\formulahendry.code-runner-0.11.2
-> first make a copy of the file!

Edit this file using Visual Studio Code. (-> copy the directory path from the Windows-Explorer to the "Open File" )

Go to Line 129, 130 and 131 (about) and change the entries to somthing like that:
( replace all "&&" by ";" - set additional the path ; - remove $dir(before$fileNameWithoutExt) for the last call - and set "artificial" double quotes "...." by " and .... " - add & .\ in front of the Filename [ & ".\Filename"] ) :

-> The $dir$fileNameWithoutExt command doesn't work properly! Double quotes ("...") are placed wrong.

"c": "cd $dir ; gcc $fileName -o $fileNameWithoutExt ; $Env:PATH += $dir ; & ".\$fileNameWithoutExt"",
"cpp": "cd $dir ; g++ $fileName -o $fileNameWithoutExt ; $Env:PATH += $dir ; & ".\$fileNameWithoutExt"",
"objective-c": "cd $dir ; gcc -framework Cocoa $fileName -o $fileNameWithoutExt ;$Env:PATH += $dir ; & ".\$fileNameWithoutExt"",

Close and restart the program twice (really!! / do it / don't think about).

Result of the output:
Windows PowerShell
Copyright (C) 2009 Microsoft Corporation. Alle Rechte vorbehalten.

PS C:\my_Visual_Studio_Code> cd "c:\my_Visual_Studio_Code\5_hello_CPP" ; g++ 5_helloworld.cpp -o 5_helloworld ; $Env:PATH += "c:\my_Visual_Studio_Code\5_hello_CPP" ; & ".\5_helloworld"

hello world -
PS C:\my_Visual_Studio_Code\5_hello_CPP>

Thanks a lot bro. Literally man you nailed it...Thanks again.

atharvabhomle · 2021-04-20T17:26:55Z

Tested for Windows 7 / Visual Studio Code version 1.53.2

Search in the following directory for a file "package.json":
C:\Users\Name_of_your_Computer.vscode\extensions\formulahendry.code-runner-0.11.2
-> first make a copy of the file!

Edit this file using Visual Studio Code. (-> copy the directory path from the Windows-Explorer to the "Open File" )

Go to Line 129, 130 and 131 (about) and change the entries to somthing like that:
( replace all "&&" by ";" - set additional the path ; - remove $dir(before$fileNameWithoutExt) for the last call - and set "artificial" double quotes "...." by " and .... " - add & .\ in front of the Filename [ & ".\Filename"] ) :

-> The $dir$fileNameWithoutExt command doesn't work properly! Double quotes ("...") are placed wrong.

"c": "cd $dir ; gcc $fileName -o $fileNameWithoutExt ; $Env:PATH += $dir ; & ".\$fileNameWithoutExt"",
"cpp": "cd $dir ; g++ $fileName -o $fileNameWithoutExt ; $Env:PATH += $dir ; & ".\$fileNameWithoutExt"",
"objective-c": "cd $dir ; gcc -framework Cocoa $fileName -o $fileNameWithoutExt ;$Env:PATH += $dir ; & ".\$fileNameWithoutExt"",

Close and restart the program twice (really!! / do it / don't think about).

Result of the output:
Windows PowerShell
Copyright (C) 2009 Microsoft Corporation. Alle Rechte vorbehalten.

PS C:\my_Visual_Studio_Code> cd "c:\my_Visual_Studio_Code\5_hello_CPP" ; g++ 5_helloworld.cpp -o 5_helloworld ; $Env:PATH += "c:\my_Visual_Studio_Code\5_hello_CPP" ; & ".\5_helloworld"

hello world -
PS C:\my_Visual_Studio_Code\5_hello_CPP>

i encountered same problem but in your first step the file you have referring is folder as i can see. I hve attached SS now tell me what to do?

Chruftl · 2021-04-20T20:07:31Z

Hello, sees you have a newer Version of the coderunner. (......code-runner-0.11.2 -> ...... code-runner-0.11.3) So open the directory that you marked and continue as discribed. C. Baumeister Gesendet: Dienstag, 20. April 2021 um 19:27 Uhr Von: "atharvabhomle" ***@***.***> An: "formulahendry/vscode-code-runner" ***@***.***> Cc: "Chruftl" ***@***.***>, "Comment" ***@***.***> Betreff: Re: [formulahendry/vscode-code-runner] The token '&&' is not a valid statement separator in this version. (#491) Tested for Windows 7 / Visual Studio Code version 1.53.2 Search in the following directory for a file "package.json": C:\Users\Name_of_your_Computer.vscode\extensions\formulahendry.code-runner-0.11.2 -> first make a copy of the file! Edit this file using Visual Studio Code. (-> copy the directory path from the Windows-Explorer to the "Open File" ) Go to Line 129, 130 and 131 (about) and change the entries to somthing like that: ( replace all "&&" by ";" - set additional the path ; - remove $dir(before$fileNameWithoutExt) for the last call - and set "artificial" double quotes "...." by " and .... " - add & .\ in front of the Filename [ & ".\Filename"] ) : -> The $dir$fileNameWithoutExt command doesn't work properly! Double quotes ("...") are placed wrong. "c": "cd $dir ; gcc $fileName -o $fileNameWithoutExt ; $Env:PATH += $dir ; & ".\$fileNameWithoutExt"", "cpp": "cd $dir ; g++ $fileName -o $fileNameWithoutExt ; $Env:PATH += $dir ; & ".\$fileNameWithoutExt"", "objective-c": "cd $dir ; gcc -framework Cocoa $fileName -o $fileNameWithoutExt ;$Env:PATH += $dir ; & ".\$fileNameWithoutExt"", Close and restart the program twice (really!! / do it / don't think about). Result of the output: Windows PowerShell Copyright (C) 2009 Microsoft Corporation. Alle Rechte vorbehalten. PS C:\my_Visual_Studio_Code> cd "c:\my_Visual_Studio_Code\5_hello_CPP" ; g++ 5_helloworld.cpp -o 5_helloworld ; $Env:PATH += "c:\my_Visual_Studio_Code\5_hello_CPP" ; & ".\5_helloworld" hello world - PS C:\my_Visual_Studio_Code\5_hello_CPP> i encountered same problem but in your first step the file you have referring is folder as i can see. I hve attached SS now tell me what to do? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

larrabasterra · 2021-05-14T23:04:13Z

You just need to change "&&" to ";"

Thanks a lot!!!

Dhanushka-Sasanka · 2021-08-15T19:12:49Z

DONOT USE && and || any more

Try to use

&& ==== > -and
| | ===;=> -or

example
( command ) -and ( command )

Like that.

Satyajit517 · 2021-08-24T13:48:54Z

Thanks.

…

On Mon, Aug 16, 2021, 00:43 Dhanushka-Sasanka ***@***.***> wrote: DONOT USE && and || any more Try to use 1. && ==== > -and 2. | | ===;=> -or *example* ( command ) -and ( command ) Like that. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#491 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AS2XNXNMDYZ2XXRF4GJN34LT5AGTZANCNFSM4HU6ASTQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email> .

Nguyenducthang1912000 · 2021-09-13T12:46:40Z

I have a better way go to Setting -> terminal and do exactly what i did

gyrao72 · 2021-09-14T15:55:12Z

I have a better way go to Setting -> terminal and do exactly what i did

This worked for me
Thanks a lot!

imba-tjd changed the title ~~cd "c:\test\" && gcc test.c -o test && "c:\test\"test~~ The token '&&' is not a valid statement separator in this version. Jun 6, 2019

This was referenced Jun 7, 2019

[API] Terminal.name returns empty string after calling createTerminal() microsoft/vscode#75071

Closed

Errors in running c++. #492

Closed

formulahendry added bug upstream labels Jun 12, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

imba-tjd commented Jun 6, 2019 •

edited

Loading

imba-tjd commented Jun 6, 2019 •

edited

Loading

pieandcakes commented Jun 6, 2019

imba-tjd commented Jun 6, 2019

pieandcakes commented Jun 6, 2019

imba-tjd commented Jun 6, 2019

xiachangsong commented Jun 7, 2019

formulahendry commented Jun 7, 2019

formulahendry commented Jun 7, 2019

xiachangsong commented Jun 8, 2019

formulahendry commented Jun 12, 2019

rohan2017 commented Oct 13, 2019

jesusarockias commented Oct 16, 2019

xiachangsong commented Oct 16, 2019 via email

imba-tjd commented Oct 16, 2019 •

edited

Loading

NguyenManhCam404 commented Feb 6, 2020

mikr13 commented May 1, 2020

Raag007 commented Jun 1, 2020

awantea106 commented Dec 14, 2020

proggdeath commented Jan 19, 2021

Satyajit517 commented Feb 13, 2021

Chruftl commented Feb 18, 2021 •

edited

Loading

sbccas commented Feb 19, 2021

hiteshkumawatpro commented Feb 22, 2021 •

edited

Loading

SahilKesarwani commented Apr 17, 2021

atharvabhomle commented Apr 20, 2021

Chruftl commented Apr 20, 2021 via email

larrabasterra commented May 14, 2021

Dhanushka-Sasanka commented Aug 15, 2021

Satyajit517 commented Aug 24, 2021 via email

Nguyenducthang1912000 commented Sep 13, 2021

gyrao72 commented Sep 14, 2021

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

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

Comments

imba-tjd commented Jun 6, 2019 • edited Loading

imba-tjd commented Jun 6, 2019 • edited Loading

pieandcakes commented Jun 6, 2019

imba-tjd commented Jun 6, 2019

pieandcakes commented Jun 6, 2019

imba-tjd commented Jun 6, 2019

xiachangsong commented Jun 7, 2019

formulahendry commented Jun 7, 2019

formulahendry commented Jun 7, 2019

xiachangsong commented Jun 8, 2019

formulahendry commented Jun 12, 2019

rohan2017 commented Oct 13, 2019

jesusarockias commented Oct 16, 2019

xiachangsong commented Oct 16, 2019 via email

imba-tjd commented Oct 16, 2019 • edited Loading

NguyenManhCam404 commented Feb 6, 2020

mikr13 commented May 1, 2020

Raag007 commented Jun 1, 2020

awantea106 commented Dec 14, 2020

proggdeath commented Jan 19, 2021

Satyajit517 commented Feb 13, 2021

Chruftl commented Feb 18, 2021 • edited Loading

sbccas commented Feb 19, 2021

hiteshkumawatpro commented Feb 22, 2021 • edited Loading

SahilKesarwani commented Apr 17, 2021

atharvabhomle commented Apr 20, 2021

Chruftl commented Apr 20, 2021 via email

larrabasterra commented May 14, 2021

Dhanushka-Sasanka commented Aug 15, 2021

Satyajit517 commented Aug 24, 2021 via email

Nguyenducthang1912000 commented Sep 13, 2021

gyrao72 commented Sep 14, 2021

imba-tjd commented Jun 6, 2019 •

edited

Loading

imba-tjd commented Jun 6, 2019 •

edited

Loading

imba-tjd commented Oct 16, 2019 •

edited

Loading

Chruftl commented Feb 18, 2021 •

edited

Loading

hiteshkumawatpro commented Feb 22, 2021 •

edited

Loading