dumb-jump VS eglot

TLDW It describes the dumb-jump emacs package: https://github.com/jacktasia/dumb-jump

I use lsp for C++, but for jump to definition I like dumb jump, because it works.

Oh, I forgot to mention, I have also found dumb-jump to work pretty well for Xcode projects, with no configuration.

I don't really have any trouble using Emacs on the "modern" C++ codebases that I'm working on. I've tried lsp-mode and eglot with clangd but found that really all I need is a little bit of elisp to call clang-format, dumb-jump (<https://github.com/jacktasia/dumb-jump>) to jump to definition, and project-compile to build the project and collect warnings/errors into a buffer.

> 2. No language server (apparently it's just impossible due to the way the language works). Tbh, I'd be happy with just "Go to definition" but alas, no-can-do!

Emacs' dumb-jump appears to have some basic support for go to definition: https://github.com/jacktasia/dumb-jump/blob/master/dumb-jump...

But out of curiosity, what is the issue from a technical point of view?

For jumping between function definitions I use dumb-jump, which usually just works. I configure dumb-jump to use ag for its searching which makes it work very quickly.

Mark ring may be what you want. If you want to jump around a code base, Dumb Jump is great: https://github.com/jacktasia/dumb-jump

dumb-jump: another tool based on ripgrep, this one defines regexes for what definitions look like in a bunch of languages. This gives you a primitive jump-to-def functionality without any setup (except installing ripgrep). The pros and cons are roughly the same as rg.el and deadgrep: you might not jump to exactly the thing you want (if there are multiple choices, you can select the definition you prefer), but it requires no setup and is pretty fast.

I recommend https://github.com/jacktasia/dumb-jump

While I have no idea about tags, I want to say that you may find something as simple as dumb-jump[1] does what you want most of the time.

[1] https://github.com/jacktasia/dumb-jump

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