haskell-language-server VS coc.nvim

Indeed, there is a lot of room for improvements. But I just wanted to acknowledge and thank the work of those involved in HLS which IMHO was a game changer in that regard.

Specifically, gchup and HLS are both opensource community efforts. If you want to see HLS work with ghc-9.2.5, you may want to ask https://github.com/haskell/haskell-language-server or, better, provide them a PR that builds HLS with ghc-9.2.5.

Sadly ghcup tui is not available on windows, but you can check the available versions with ghcup list. Hls lists the compatible versions of ghc at their github releases. For 1.8.0.0 I went with 9.4.2. To install it and set it to default you have to use the ghcup install ghc 9.4.2 then the ghcup set ghc 9.4.2. Hopefully this will be useful to someone with the same problem.

Here's an issue I created for it: https://github.com/haskell/haskell-language-server/issues/3348

The code is executed by HLS, see https://github.com/haskell/haskell-language-server/blob/master/plugins/hls-eval-plugin/README.md and then its markdown/html output is displayed by VS Code.

As you can see there, Shake is also a good fit for Cabal scripts. And Cabal scripts work better in 3.8. There are still issues loading them with HLS, but hopefully not for long. For this reason, I also have a build.sh which wraps that, allowing the script to be loaded via GHC directly, but I look forward to being able to remove this.

AFAIK the latest GHC version which the haskell language server (which is what the vs code extension uses) supports is 9.2.2, so not yet, I'd say.

As far as I could see this bug is already reported. It is about stack not being able to handle multi crate project.

All of coc.nvim's extensions are as closely mirrored to the convenience of VSCode extensions. This convenience matters, as you must not be spending time on "tool pain" on work hours. Copy whatever configs you need from the readme to get keybinds set up.

I'd say just try to copy that code from nvim-cmp readme as is (unless you're using a different package manager ofc) and see if it works for you. If you decide that you've spent too much time on it, you could give https://github.com/neoclide/coc.nvim a try instead. It has vim support as well, and as far as I know it comes with a lot of stuff included.

It takes some time to set up nvim to feel like VScode, so don't expect this to happen overnight, you need a lot of plugins because VScode provides a ton of tools out of the box. I would recommend the plugin Coc.nvim. That gets you most of the way there right away. When you're comfortable, nvim provides built in tools, but they require more configuration.

I use coc.nvim and disable everything but omnicompletion using the following ~/vim/coc-settings and by only adding the TAB and some other navigation key maps.

coc: health#coc#check 3 ======================================================================== 4 - OK: nvim version satisfied 5 - ERROR: Unable to detect version of node, make sure your node executable is http://nodejs.org/ 6 - ERROR: Javascript entry not found, please compile coc.nvim by esbuild. 7 - ERROR: service could not be initialized 8 - ADVICE: 9 - Use command ":messages" to get error messages. 10 - Open a issue at https://github.com/neoclide/coc.nvim/issues for feedback. 11

Did you read this?

coc.nvim and its extensions will get you the farthest. It's a partial port of VSCode backend functionality.

Set up pyright LSP. Either use https://github.com/neoclide/coc.nvim or https://github.com/neovim/nvim-lspconfig. The former is easier to set up and the latter is native to neovim and you can use it with lots of more plugins.

I've been using coc.nvim along with the coc-solargraph plugin. These work well for me and provide very good code completion and error highlighting. There are some key intellisense features that aren't available (or I don't use them), but these two plugins do well enough for my purposes.