-
Notifications
You must be signed in to change notification settings - Fork 206
Windows 10, VS Code: HIE server crashes - spaces in path not handled properly? #565
Comments
Are there any useful messages in |
@johnsonwj, there is no If I move A little knowledge can be a dangerous thing, but I wondered in repository
should be modified to put quotation marks around the string on Windows? - given:
but I did not know how to test that idea. |
Probably it's really vscode hie plugin - reproducable on vscode, not reproducable with neovim on the same project, same hie binary, same path. |
I'll open an issue in that repository then. |
Does anything need to be done in hie for this? |
Hi, not sure how but i just tried:
And the hie server is launced in both cases. Hie version:
vscode version: 1.38.1 So it seems this is fixed, i think we can close it, @mpilgrem feel free to reopen if you still are hitting it |
I have almost identical setups on two Windows 10 machines. HIE/Haskell Language Server (HLS) works with VS Code on one, but fails on startup on the other with the following 'notification' message ('HelloWorld' is the name of the test Haskell project, created with
stack new HelloWorld
):The Haskell HIE (HelloWorld) server crashed 5 times in the last 3 minutes. The server will not be restarted.
and messages in 'OUTPUT' ('Haskell HIE (HelloWorld)') like:
One difference between the setups is that there is a space in the path on the one that is failing and not in the one that works. That is,
hie.exe
is located (on the one that fails) at:and the 'output' above seems to reference only the part of the path after the space.
I wondered if HIE or the Haskell Language Server extension for VS Code was failing to treat paths with spaces correctly?
For reference:
hie.exe --version
isVersion 0.2.0.0, Git revision 753deb91f9b9b39f14722315277d9fd587716bde (1341 commits) x86_64 ghc-8.2.2
code --version
is1.23.1
,d0182c3417d225529c6d5ad24b7572815d0de9ac
,x64
The text was updated successfully, but these errors were encountered: