dotfiles VS lsp-docker

NixOS. If you still need Docker you can define and manage that via Nix too. I love it, both for this and managing development environments. Happy to answer any questions.

With Nix we have a shell.nix in the root of our repo describing all of the project's system dependencies. It looks something like this. You can pin nixpkgs with Flakes (think lockfiles) or by hardcoding a specific revision. We do the latter because I didn't want to complicate the Nix install for everyone by requiring they enable experimetnal features.

Nix, for example updating from rls to rust-analyzer.

I agree that the documentation story could be better. I also think it's a great shame that the language isn't statically-typed, so to understand how to use something I have to inspect its source code.

I've found it to be quite flexible though. For example, here's a commit in which I apply a patch to a tool to solve a problem that the derivation hadn't taken into account (and absent a home-manager solution): https://github.com/samhh/dotfiles/commit/867dd3b4d4b3942a0aa...

You may like to look at my newsboat config. It's biased towards FP and Linux.

Sure thing, I manage it in my dotfiles repo here.

I wonder if you'd have better luck if you built your xmonad as a proper Haskell app and didn't use the built-in --recompile stuff. It's not Nix, but see here an example of how I'm doing that.

Here's my config: https://github.com/samhh/dotfiles/blob/master/home/.config/git/config

This is possible for quickfix, see my dotfiles commit here.

I believe this has cost me a ton of time but I did learn a lot along the way. lsp-docker highest level function is lsp-docker-start. It calls lsp-workspace-root which calls buffer-file-name which, if starting from a dired buffer, returns nil so lsp-workspace-root returns nil and the LSP server is not started.

I'm trying to figure that out right now. There is lsp-docker which is designed (I'm still half guessing) to have a separate container hold the language server. What I want is a pre-existing container to hold the server. There is partial code in that repo to do that but it appears not fully baked.

If you're on WSL, you may want to take a look at something like lsp-docker which bypass all quirk of Tramp and works directly with your files in WSL. I've never been able to make Tramp work reliably (too much hanging with or without lsp-mode) from Windows -> WSL so bypassing it provides a much better experience.

This is a reasonable point, and something that is being worked on. I definitely think Docker can provide LSP servers as necessary, we're just not quite there. This is something that I'm interested in working on, though I'm not the only one: https://github.com/emacs-lsp/lsp-docker

Yeah, I'm a NixOS user, and nix helps a lot with managing LSP servers on my system at the point that this is not a issue for me, but I agree a solution runing then in a docker or something would fit nice as well, we already have this conecpt: https://github.com/emacs-lsp/lsp-docker/

[0] https://github.com/emacs-lsp/lsp-docker#docker-over-tramp-tbd