-
-
Notifications
You must be signed in to change notification settings - Fork 368
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
Stack install hls (upload package to hackage/stackage) #400
Comments
That would be a nice feature, it needs the package in hackage and, optionally, in stackage. That, in turn, needs that hls uses ghcide from hackage instead as a submodule. |
We could continue to use ghcide as a submodule, just make sure we release syncronised? The flexibility of upgrading ghcide quickly seems like its currently pretty useful, so I'd be a bit sad to give that up. |
Yeah, i overlooked it; just sync them will be enough |
It turns out the next release (#567) will use the hackage ghcide version, so we could release hls to hackage (by coincidence this time so maybe it will be discontinued) |
There is some discussion about the issue of the possible mismatch between the project ghc and the used on to compile hls: #567 (comment) |
hls is already in hackage and we have too much extra-deps to upload to stackage in short/medium term so closing this |
I'd like to be able to type
stack install haskell-language-server
in a stack package and have a version of all the tools I need for the version of GHC that package is using and put in a place where it will get found, if I change my LSP setup (in neovim) fromcmd = { "haskell-language-server-wrapper", "--lsp" }
tocmd = { "stack", "exec", "haskell-language-server-wrapper", "--lsp" }
The text was updated successfully, but these errors were encountered: