evil-guide VS emacs-which-key

2. the leader key https://github.com/noctuid/evil-guide#leader-key

these are random search results that may or may not be authoritative, but they should be a good start.

Doom uses Evil-mode for vim emulation. https://github.com/noctuid/evil-guide is a good guide for translating between vim concepts and Emacs.

I'm not aware of a guide specifically for non-vim users, but pretty much any vim guide will be helpful - it's just best to avoid parts on vimscript, as evil isn't configured using that. Even though it introduces itself as a guide for Vim users, I still think https://github.com/noctuid/evil-guide is worth a read. As for packages which complement evil, most are named with evil as a prefix, so you can browse melpa with that in mind. One exception that comes to mind is lispyville, which provides an evil approach for editing s-expressions. evil-cleverparens is also worth a look. Feel free to ask any questions on the evil issues page too!

Evil is a complex machinery build by vim nostalgic refugees, so familiarity with Vim's modal editing model is still recommended. I like this, even if it's not a tutorial: https://github.com/noctuid/evil-guide

I'd recommend reading noctuid's evil guide, particularly the link to the spacemacs keymap guide and the mention of the commentary on evil-core.el

It’s probably worth understanding what evil is doing so you can make your own key bindings for packages you find. I personally don’t think evil is obscuring things for me because I’ve gotten pretty good at using the introspection features of emacs to look at what everything is doing. The guide from noctuid was a good reference when I read it https://github.com/noctuid/evil-guide.

Set aside a little bit of time to learn properly how Emacs and evil-mode work together. Not sure if you've seen it, but here's an excellent guide for transitioning from Vim to Emacs with evil-mode. It's by the author/maintainer of general.el.

A bit unrelated to your question, but if you are having trouble with keybindings I really recommend this read. Also, if you use evil-mode, reading evil-guide is really worth it as well, to understand how to configure things correctly.

This should make the porting process easier https://github.com/noctuid/evil-guide

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?