-
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
HLS automatic version detection failing #1151
Comments
Thanks for the bug report! At a first glance, it looks like Can you try to go to |
Yes, it is set to |
Yes, but vscode-haskell will also launch the correct HLS and GHC version based on what you have in |
Right, but if I have it set to |
If you select
Could you elaborate on this? In |
I think I may have indeed misunderstood something about how the versions are used. It seems to me that when set to
I used the wrong phrase here; I meant when running I totally understand that by using the See my path and binaries:
|
Yes, it looks for |
Got it, thank you! I appreciate the help, and I suppose this is a non-issue |
Happy to help, feel free to open another issue when you encounter problems! |
I'm still new to Stack/HLS/GHC, so my apologies if some of this is incorrect. I am attempting to have VSCode cleanly work with Stack out of the box. I installed
ghcup
binary per Haskell site and followed along to also install Stack. I have two projects, one that targetslts-22.11
(ghc-9.6.4
) and one that targetslts-22.34
(ghc-9.6.6
) in theirstack.yaml
files. I also found that 9.6.4 is supported by HLS 2.6.0.0 and 9.6.6 is supported by 2.9.0.1. Depending on which of those two HLS versions I have set as active on Stack, the extension will work for the corresponding project and fail for the other one due to not finding a proper HLS version. So in this configuration, the project withghc-9.6.4
will not work with the VSCode extension:ghcup tui
information:It looks like it successfully finds the HLS candidate but then doesn't end up selecting it. Separately, it does work when manually specifying the toolchain like in the README, i.e. adding this to each workspace's settings.json:
But I was under the impression that it should work automatically based on the Stack installs. Please let me know if there's anything I'm missing or other info that would be of help. Thanks!
Full debug when running in above config on
ghc-9.6.4
on macOS Sequoia (Intel based):The text was updated successfully, but these errors were encountered: