-
-
Notifications
You must be signed in to change notification settings - Fork 391
Fails to load when cabal file contains non-ASCII characters #1926
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
Comments
Thanks you for reporting the issue. Until the bug is fixed a possible workaround could be generate an explicit |
Thanks for the workaround, that does work. |
Hmm, i cant reproduce with hls 1.1 in windows adding this line to my cabal file: EDIT: hls-1.2.0 works for me too
|
Can confirm having the same issue with the VSCode extension on NixOS. |
Solved by installing nixpkgs' |
It seems this is not reproduced with newer hls versions, feel free to reopen ion other case |
FYI, I just ran into this bug with hls 1.7.0. The log below shows the cabal file as text and hex dump. It turned out that the problem was that the VM I was using had locales set to
|
I also seem to be having the same issue, having built 1.7.0.0. from source. |
I'm hitting this. haskell-language-server 1.8.0.0's haskell-language-server works fine from command line but when run from within VSCode it results in
It's possible that the problem traces to the builtin gen-hie code supplied by implict-hie (and possibly further to Cabal-syntax). It is POSSIBLE that an explicit hie.yaml file containing, in my case nothing more than
might act as a workaround suppressing the implicit hie code path. It's working? but if so, fragile. Unclear whether something Nix is doing might be triggering the localization issue; code developed on the underlying Fedora system works (or was working) fine. |
I have an example here of a project that crashes haskell-language-server because the cabal file contains an em dash. If I remove the offending character, then HLS works.
The text was updated successfully, but these errors were encountered: