emacs-gdscript-mode VS emacs-which-key

Do You have any advices how to configure lsp server for gdscript in emacs? On module site (https://github.com/godotengine/emacs-gdscript-mode) is only enigmatic:"To use it, you need to install lsp-mode on top of gdscript-mode and configure it. To install and configure lsp-mode, see the lsp-mode documentation." What does it mean "install lsp-mode on top of gdscript-mode"? Are there any special commands or techniques to do it in emasc? Lsp instalation page says gdscript lsp server must be installed manually and redirects user to main page of godot's github.

The script-editor for GDScript in Godot is pretty basic. I think it is OK and it has some useful features, but I often switch to Emacs (with gd-script-mode) when I need to do some bigger edits. The Godot developers are never going to be able to compete with any of the big editors. What they can do is to offer good integration with their scripting language and the Godot engine of course and they are doing that (which is why I use their script editor most of the time).

I use (doom) emacs for writing gdscript on linux and osx, without issues. With gdscript-mode (https://github.com/godotengine/emacs-gdscript-mode) and lsp support, you get most of the features offered by the editor. I spent some time in the built-in editor when first starting with godot, but I missed vim-style keybindings and general extensibility.

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?