-
Notifications
You must be signed in to change notification settings - Fork 90
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
Windows 10, VS Code: HIE server crashes - spaces in path not handled properly? #84
Comments
I'm getting the same errors out of nowhere - one minute HIE was working, the next it refuses to start after five or six times quitting and relaunching VSCode. This happens frequently but usually the problem goes away within 10 minutes or so. Not this time. I found a log file PS. I am not on Windows nor using a path with spaces. hie v. 0.2.0.0 Also, resolver is lts-12.0 |
The new |
OK, I remade hie (to version 0.2.1.0) and now I have an
Which makes sense since I don't have a Update: |
@Rhywun hie should start without ghc in path using stack (since haskell/haskell-ide-engine#1496) |
As noted in haskell/haskell-ide-engine#565, HIE/Haskell Language Server (HLS) does not work with VS Code if
hie.exe
is on thePATH
but on a path with a space in it. It fails on startup with the following 'notification' message ('HelloWorld' is the name of the test Haskell project, created with stack new HelloWorld):and messages in 'OUTPUT' ('Haskell HIE (HelloWorld)') like:
hie.exe
is located at:and the 'output' above seems to reference only the part of the path after the space.
If
hie.exe
is moved to a location with no spaces in the path, everything then works as expected - which is an easy work-around but not the desired behaviour.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: