emacs-which-key VS lsp-mode

I think which-key already solves exactly that: https://github.com/justbur/emacs-which-key

As for the "complicated keybindings general" -- I assume because remembering things like C-x C-s is hard because of the shifted keystrokes? I get that, and there is in fact a solution for less used keybindings which I love, called 'which-key' https://github.com/justbur/emacs-which-key

I would recommend installing the which-key package, which is a fantastic discoverability aid. If you ever want an example config to get some inspiration, I have one here: Emacs Bedrock

Make sure you have which-key installed and turned on. When using a keybinding that has a prefix (like C-x or C-c), it displays all the keybindings that start with that prefix.

which-key for the shortcut menus

there are some packages to help with the keybings, which-key shows a list of keybind and its command and (guru-mode)[https://github.com/bbatsov/guru-mode] enforces to use the "best" keybind, for exemple, it forces you to use C-n to move the cursor, blocking you to use the down key, and if you press the down key, it show a text in minibuffer to the best keybind.

Thanks for confirming, I think it's an issue in which-key itself: https://github.com/justbur/emacs-which-key/pull/166

If you haven't already, definitely check out the package which-key.

> even though I'm a terminal user ... I really like the discoverability of GUIs, and that's where a good GUI is unbeatable by CLI.

CLI has poor discoverability? Sure; but even on the terminal, discoverability can still be good:

A couple of nice examples of discoverability in keyboard-focused programs:

- emacs' which-key[0]; there's a vim port[1] too. This shows you (some) of the available keybindings for the next input, and a short label. So you don't have to remember what `SPC h p ...` or all the options under `SPC f...`.. but it still helps to recall that `SPC h` is for 'help' related commands, `SPC f` for file related commands.

- emacs' magit[2][3]. Magit is so good at discoverability, that I'd rate it as the best tool for using git with. I've learned more about git from using it.

[0] https://github.com/justbur/emacs-which-key

[1] https://github.com/liuchengxu/vim-which-key

[2] https://magit.vc/

[3] https://emacsair.me/2017/09/01/magit-walk-through/

Am I right in thinking this is quite similar to which-key?

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?