-
-
Notifications
You must be signed in to change notification settings - Fork 369
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
Spaces in auto-generated cabal command failing #3961
Comments
Hi, thank you for your bug report! This is an issue with HLS, moving it to the main repo. |
Hm, I am wondering whether this issue is specific to a cabal version and whether we can reproduce it on linux as well. |
In a test project Why am I not first checking for issues in hie-bios: I think we are using |
I'd expect that to work because you added quotes around the parameters with spaces. The command that hls is running doesn't have quotes in it, that's the problem. By the way, I'm using ghc 9.6.3, cabal 3.10.2.1, and hls 2.5.0.0. |
The logs do not give the full picture of what command is being run. If the build dir or the ghc path cannot be resolved, cabal should fail much earlier in my expectation. |
It may be even a GHC bug: https://gitlab.haskell.org/ghc/ghc/-/issues/24265 Stack seems to have users that experience a similar issue: commercialhaskell/stack#6380 |
Your environment
Which OS do you use:
Windows
Steps to reproduce
I don't know how to reproduce this, most likely the cause is that I have a space in my Windows username so %APPDATA% has a space in it. The extension was working fine until today, though, so I'm not sure why this never happened before.
Expected behaviour
When I open my project, the extension automatically runs the following command:
This command should finish successfully
Actual behaviour
The command fails because of the space in the path
C:\Users\Anand Swaroop
.Include debug information
Execute in the root of your project the command
haskell-language-server-wrapper --debug .
and paste the logs here (you can find the executable location here):Debug output:
Paste the contents of extension specific log, you can check instructions about how to find it here
Extension log:
The text was updated successfully, but these errors were encountered: