doom VS use-package

Otherwise, please try out Doom Emacs :) https://github.com/hlissner/doom-emacs/

Doom Emacs is a fantastic distribution of Emacs which makes performance improvements on vanilla emacs, probably making it faster than your own configuration. The installation process and migrating your config would be simple IMO, so you may want to give it a try... https://github.com/hlissner/doom-emacs/

I prefer https://github.com/d12frosted/homebrew-emacs-plus which works nicely with https://github.com/hlissner/doom-emacs

Doom emacs and Spacemacs are "emacs distributions": when installed you get an entirely pre-configured emacs with all of the nice bells and whistles already there for you. I personally started with spacemacs and then moved to my own emacs config later. One massive caveat for spacemacs is that it is highly intergrated with the "evil" package, which means it uses vim keybindings. While you can disable "evil-mode", the configuration will be greatly hindered without it.

I haven’t used Emacs in about 5 years. Had to look up Doom Emacs.

It looks nice.

https://github.com/hlissner/doom-emacs

It may or may not be your long-term environment but for someone looking for Vim keybinds and an easy on-ramp, you can dip your toes via doom-emacs and enable the relevant modules. I'd start with :lang javascript[1] and web with +lsp and :tools lsp[2].

I just had a very odd thing happen to me on GitHub.

I accidentally closed my browser so I reopened it with Undo Tab Close, and GitHub's tab title was labeled "Your account recovery is unable to load" for a very brief moment. Then a GitHub error site with a pink unicorn loaded. The URL which was supposed to load was https://github.com/hlissner/doom-emacs which I had tried to load about 15 minutes or so.

Maybe something like https://github.com/hlissner/doom-emacs can be a good idea if you don't want to start from scratch.

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.