eglot VS straight.el

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.)

Very dated and next to useless on large complex CPP codebases. Use a language server. I recommend the straight package manager. https://github.com/radian-software/straight.el

Have you tried using straight.el or the heir-apparent Elpaca? These package managers will check out the git repo of said packages, and you can easily fork them with magit and forge. That's that I do to contribute to packages.

Thank you for your time addressing all those issues and sorry if questions were misinformed - I found your advices invaluable to understand design goals of package managers in emacs.

I used straight.el, now I use Elpaca.

Doom Emacs is not a package manager. It has a package manager, which is based on Straight.el.

I have been crafting my emacs config for about 10 years. I started with vanilla and intentionally stayed away from frameworks. About two years ago I declared config bankruptcy and went down for a rewrite using use-package and straight.

First install straight.el (https://github.com/radian-software/straight.el)

ref: https://github.com/radian-software/straight.el https://github.com/jwiegley/use-package

If you use straight and override package, you'll get a lot of your desired functionality for free. Straight's docs are excellent. I started banging away on my own setup from scratch, and while not perfect, it does what I want and the total startup time is about 1.5 seconds without doing anything to try to optimize it. If you want to see it, check it out here. Like I said, there is lots of room for improvement, but it does work for me.