haskell-language-server VS lsp-mode

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.

I believe you've bumped into this issue: https://github.com/haskell/haskell-language-server/issues/2857

I love emacs for the fact that I can use it with many different languages. I get my IDE like features (auto-complete, linting, formatting etc.) from lsp-mode. You can configure emacs by writing elisp in your .emac dotfile in your home directory. Here is my messy config file. The general tactic is to copy snippets from other people. I don't know a good starting point for configuring, but maybe this video can give you a glimpse of what it is like. Picking a feature and getting it working was what helped me when I first started out with emacs. evil-mode was the first thing I installed, because I like vim.

Since you are doing code development, the first things to go for would be setting up your emacs packaging (installing use-package and melpa (use-package's documentation covers this) so you have more packages to choose from (do be careful to not just pick things willy nilly but research them a bit first)) and then setting up lsp-mode. lsp-mode lets you use LSP servers for the specific programming languages you work with in a somewhat unified fashion. You then need to install and setup the LSP servers for the languages you use, and possibly install language specific Emacs packages as support (note, Emacs has builtin functionality for many).

And first of all, I'm trying to understand, how is it connected to https://github.com/emacs-lsp/lsp-mode? I'm sure, that existed lsp implementations already parse source code. Why TreeSitter?

Debugging (kind of an IDE feature) is a little harder. Out of the box, Emacs can at least debug emacs-lisp (with built-in features) and C (via gdb integration). Beyond that, take a look at dap-mode for other language options. Similarly, take a look at lsp-mode or eglot for code completion, more advanced linting, etc.

lsp-sourcekit ;; completion stops working after lsp server returns an error #3028

If you use emacs, I recommend to get some modern goodness by installing lsp-mode (or eglot) to interact with language servers and then install a latex language servers like texlab. This in my expericence really improved the autocompletion so I don't feel like I loose anything over using vscode, texlab or overleaf .Recently I also switched to lsp-ltex for language-tool integration. All those tools lsp servers can also be used from other editors with lsp support, so use what you prefer. I would only recommend emacs to those who want a fully customized and keyboard driven experience and are not afraid to eventually modify some lisp code. But it has its unique advantages, many editing tools and in addition to the still great auctex also cdlatex for super quick math typesetting.

One caveat I had was with TypeScript - eglot can't run more than one LSP server at the same time, so you have to use a separate package for ESLint if you use it along tsserver. But I think that's a perfectly fine solution and it honestly works better than lsp-mode, which required me to install a separate package just to get errors to show up properly.

I couldn't reproduce it with my setup. Just for the reference, I use Doom ba35f12be with Emacs 29.0.50 76b7a5936 on Debian 10. Specifically, lsp-mode 68bdac0f8, lsp-ui d8cce7dc1. I use monospace Iosevka TTF font for both italics and regular faces.

The first step is choosing whether to use the eglot or lsp package for your LSP client. After choosing this, you will need an actual LSP server installed. The two main (and best) contenders are ccls and clangd. For both the client and the server, the choice you make is personal, and it's quite easy to switch between them, considering a simple configuration.