use-package VS evil-collection

Another way would be to redefine parts of the bind-key macro or its use-package support functions

The package-install call installs use-package that provides a utility of the same name to make it easier to manage packages. It's admittedly a little overkill for this specific config, but it's a cheap investment that sets you up for later success.

Granted, the Doom macro makes your code looks nice and compact. But you can get very close to that just by using do-list and define-key together. Or by using the bind-key.el package, which is included with Use-package.

> Deps is well documented.

> The issue I personally found is that I needed to look at a bunch of OS project's deps.edn to see how people commonly structure things. Other than that it is a simple tool.

This strikes me as a contradiction, because if it was well documented you wouldn’t need to look at other people’s configs to see how to use it.

My experience with deps.edn is that every time I start a project and make a deps.edn file, I immediately draw a blank and don’t know how to structure it, so I open ones from other projects to start lifting stuff out of them.

I still don’t know how to reliably configure a project to use nrepl or socket repl without just using an editor plugin. I definitely have no idea how to use those in conjunction with a tool like reveal.

To me, none of that is simple. Simple would be like Emacs’ use-package. With that I know how to add dependencies, specify keybinds, and do initialization and configuration off the top of my head. And it has really nice documentation with tons of examples.

https://github.com/jwiegley/use-package

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).

I'm using use-package as my package manager and the package ligature for the ligatures.

I have been crafting my emacs config for about 10 years. I started with vanilla and intentionally stayed away from frameworks. About two years ago I declared config bankruptcy and went down for a rewrite using use-package and straight.

ref: https://github.com/radian-software/straight.el https://github.com/jwiegley/use-package

use-package! is a macro over use-package, and respect its syntax, with a few additions. Useful reference on use-package keywords.

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.