-
For the past few weekends, I've been following along with Emacs from Scratch from System Crafters, looking at some of Prot's stuff, reading the manual where needed, copiously using `describe-function/variable/etc`, reading a bunch of configs that I've found that people have mentioned as being inspirations for them. Things are moving along mostly smoothly and I'm making really great progress and it feels really fantastic to start slowly tailoring things to how I want them....
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
- Whenever I have downtime, I'd pick one from this list and try to implement it (mostly, for fun). Initially, it was intimidating, had no idea what I was doing but that get's better. - Before I knew it, my "https://github.com/anonimitoraf/doom.d/blob/master/config-sections/misc.org" config has grown to a couple of hundred lines.
-
Now I'm a happy Doom user that also has a ~2k line personal config file (tip: open that in emacs so that you can collapse some of the irrelevant headers at the start), so I definitely wouldn't say that it makes it hard for you to wedge your own stuff in, but it's certainly not as simple as when you're making your own config (although it's close).
-
For example, if you look at Doom's Clojure module, which is broken down into a package-declaring file and a package-configuring file like every other module, you'll see that it's doing things that you could easily recreate in a personal setup too. You can't exactly copy-paste it; the package! and use-package! macros are Doom's own, but they're thin wrappers around the vanilla use-package so you could migrate their functionality pretty easily. Same for map! that's for keybinds, which is a wrapper around general.el.
