-
-
Notifications
You must be signed in to change notification settings - Fork 219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[2.0] Jack-in command quoting fails on some Windows setups #195
Comments
So what i could gather is that the jack-in execute the same command that is described in the wiki. When i execute this in the powershell this is the result: But when i change the command like this: |
Thanks. Do single quotes work in the regular |
No there i get the java.lang.RuntimeException: EOF while reading Exception. |
Hmm, so how many windows scenarios are there? |
4 i would say:
For 4 and 1 you can use double quotes. For 3 i have no idea but would guess double quote works there too. Only exception seems to be powershell. |
So, the 3 is the same as WSL? |
Yes to both :). |
What determines if the jack-in is performed by one or the other of these? Are there vscode settings for this? I am trying to figure out how to tell what quoting to use. |
Alternatively, how to instruct the user to start Calva for it to work. |
This is the setting: terminal.integrated.shell.windows |
So, if you manipulate that setting the jack-in task is affected? |
Hi. When I try to use the jack-in feature on Windows 10, I'm getting the following error. I'm not sure if this is related, but it looks like it may be.
|
Update: Using single quotes worked for me as well. |
I spent some time trying to come up with a format that would work at least in both powershell and cmd, and unfortunately could not get anything to work. So it seems the best method would be, as stated above, read the terminal environment and output the appropriate command. |
I'm also using Windows and encountered the EOF issue. Here's the full log:
Interestingly, if i paste the upper command into cmd, it works fine. It I paste it into the powershell, I get a different error:
This would indicate to me that it is a problem with the vs-code task runner and not the shell itself. The integrated shell that I'm using is the power shell. I hope, that added something useful for you. PS: For brevity and because I don't think it's, I omitted the full stack trace. If you're interested in the full stack trace, just give me a shoutout :) |
@felixlinker It is an issue with the way quoting works in Powershell, mostly. A workaround is to set your default shell in VSCode to cmd. Then the jack-in command should work. The command will work in powershell if you replace the double quotes on the outside to single quotes (leave the escaped ones as double quotes). Something like this might work in powershell for you (if I didn't make a typo):
|
Placing this here for Windows people to fill in more details.
The text was updated successfully, but these errors were encountered: