lsp-docker VS eglot

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

Recently I stumbled upon this issue:

https://github.com/joaotavora/eglot/discussions/1127

I don't know enough about emacs and LSP to see the full picture, but it seems that both eglot's and corfu's maintainers, assumably very competent programmers, can't find a solution for this.

I only skimmed the thread. My understanding is that LSP dumps a long list of completion candidates at once and they can't decide a cache strategy that works well with existing code...?

It could be. There are unfixed issues with eglot and corfu, and sadly not a lot of willingness to investigate.

Eglot errors when I add new Python code blocks. The error disappears when I reconnect the language server, but the same happens again when I add a new code block. My "workaround" now is that before I start working on the .qmd file, I just add a bunch of Python code blocks (for which I also have a function) and then reconnect the language server again. This way I can start working for a while until I need to add more code blocks again.

This discussion has helped with some performance issues: https://github.com/joaotavora/eglot/discussions/993.

I guess eglot doesn't support it yet: https://github.com/joaotavora/eglot/pull/839

This is not by pure chance, João is the developer of the Eglot LSP client and the breadcrumbs from LSP-mode had been requested as a feature, but as far as I remember João thought rightfully that this could be an independent package, see https://github.com/joaotavora/eglot/discussions/988

A substantial section of the community is using corfu instead of company, but I wouldn't say company is out of date by any means. In emacs 29 eglot will be a built in, which might act as a replacement for lsp-mode depending on what functionality you need.

I am currently running emacs 29 (built from emacs-29 branch) which – according to https://github.com/joaotavora/eglot – should contain the latest eglot.

Yep. You can use flymake or flycheck for that in combination with eglot or lsp-mode.

See https://github.com/joaotavora/eglot#diagnostics

(I have reported this (that is, ElDoc missing docs for callable things at point, when Eglot is enabled) as an issue recently: First on GitHub-discussions https://github.com/joaotavora/eglot/discussions/1200, then on Debbugs https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62687. But the threads are very long, so I don't recommend reading them.)