helpful VS evil-collection

If you want to programmatically create files, write to them, etc, then read the fine manual, it comes with your Emacs, has index, search and web-like navigation. It is well worth your time investing in looking up the manual, both for Emacs and for Elisp. You access the manual via C-h i. Another good thing to learn how to use is Emacs built-in help. As a minimal basic, C-h f will display information about functions, and C-h v will display the documentation for variables. You can also see where things are declared, open the source code, etc. A good alternative to built-in help is Helpful, which I suggest installing and start using too.

It tweaks Emacs GC. You can run M-x describe-variable while your cursor is at gc-cons-threshold to learn about it. If you opted-in for using "Vim bindings" (Evil mode), you can press K while in normal mode. Note that K doesn't run the describe- command in Doom, but it runs helpful-command from (https://github.com/Wilfred/helpful), which provides more context that describe- commands usually do.

The packages helpful and elisp-demos are super useful because they enhance Emacs' built-in documentation.

You can try to actually use helpful for a while. There was also a package with examples, I don't remember the name, perhaps someone else knows which I mean, that shows usage of a function where available. I remember using it and found it very useful for a while when I was learning elisp more actively. I still use helpful sometimes.

Once you got the hang of keybindings, which-key is a helpful extension (aka package) to Emacs. At this stage, there are other helpful packages and keybindings.

helpful for better help buffers

Since you seem interested, have a look at elisp-demos , too. It works in tandem with helpful.

Elisp Docs are fantastic they have documented everything while with CL most documentation is missing or only on the Web. With Emacs, one need to learn about C-h f (describe-function), C-h k (describe-key), helpful.el and elisp-demos and a new world opens. Terminology is always different, simple example: Microsoft terminology sounds like bullshit, to a Unix person.

Your primary source of knowledge will be the manual and the built-in discoverability (describe-* functions, or helpful) and of course reading the code. I'm not a manual person myself, but Emacs is one of the examples where it is truly excellent and has answers for almost everything.

It looks like that package has an issue tracker here, if you wanted to raise one: https://github.com/emacs-evil/evil-collection/issues

Honestly, I've yet to find a plugin that I use that isn't covered by https://github.com/emacs-evil/evil-collection. I love emacs, but I can't stand the chords.

Evil and Evil Collection is the nuclear option.

I still have phases where I experiment with modal editing, but I haven't messed with Evil-mode in a long time. I prefer Meow, in part because it doesn't invest everything on a single command layout. And the sample Dvorak layout meshes really well with Emacs bindings for special modes (like Dired and Ibuffer). So you don't have to install and configure something like Evil-collection just to use the same bindings everywhere.

The problem I have with evil in Emacs is that it is another layer on top of vinalla Emacs. Not many packages are designed with evil key bindings in mind. You need packages like https://github.com/emacs-evil/evil-collection and and https://github.com/emacs-evil/evil-magit and https://github.com/emacs-evil/evil-ediff to make Emacs feel more "evil". Distros like Doom and Spacemacs integrate these packages for you, but then you're even farther away from the default Emacs experience. I also find online help worse for evil bindings. To figure stuff out you often have to resort to looking at vim or neovim documentation. "Vanilla" Emacs is famously "self documenting" but last I checked evil couldn't provide useful help, within Emacs, in the same way.

Evil does interfere with bindings in some modes, but https://github.com/emacs-evil/evil-collection fixes a lot of these issues, both for built-in modes and a lot of popular third-party ones.

Oh, and stick this in your use-package for general: ;; We want SPC as a leader key, probably. So do this. It just affects what ;; keybinds are overridden by the `override' keymap functionality that ;; `general' provides. ;; ;; https://github.com/emacs-evil/evil-collection#making-spc-work-similarly-to-spacemacs ;; ;; NOTE: `evil-collection' binds over SPC in many packages. To use SPC as a ;; leader key with `general', first set these override states: (setq general-override-states '(insert emacs hybrid normal visual motion operator replace))

You might want to look into the evil-collection package.

Evil mode is incredible, but it has real disadvantages in the Emacs context. It is another layer above Emacs, which makes Emacs different from its default self. E.g. most packages don't come with evil-mode key bindings. The popular Emacs packages are handled by https://github.com/emacs-evil/evil-collection but, there is always going to be a layer of translation between how upstream describes its key bindings and how Evil binds them.