dumb-jump VS lsp-mode

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

I also tried to the solutions suggested  and , but nothing worked. I moved the (setq lsp-keymap-...) line outside (and before) use-package. I also used :config (define-key lsp-load-map...) in my use-package block. But none of them worked.

Not sure how much this might help, but lsp-mode has lsp-yaml-select-buffer-schema and lsp-yaml-set-buffer-schema commands to pick schema from a list or set from a URI. Checking the source of them might give some hints about how the same could be implemented in eglot?

Beyond that you might as well embrace the suck and install autex with a language server: https://emacs-lsp.github.io/lsp-mode/

Smart completion these days is done primarily through LSP. eglot is fairly minimal but built-in as of 29, also available via GNU Elpa. lsp-mode is another option with more integrations and a bit more fleshed out.

lsp-mode: https://github.com/emacs-lsp/lsp-mode/issues/2080

Are you running emacs-29? It has numerous speed-ups compared to emacs-28 and older versions, many of them coded by Mattias Engdegård, e.g. commit def6fa4246. I have a fresh build of emacs-29 running on Linux and a new mac with an M1 CPU, and it's stupid fast. I don't use the native-comp feature. I rarely notice any hesitation or slowness. I don't use Elpy. I do use lsp mode.

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?