I don't like custom.el. I don't like what it does. Anything in it
that's actually useful should be made persistent in my configuration
anyway. So why should I have it tracked in git? Should be set per
machine anyway.
The .config folder stores the configurations generated by various
packages. For the purposes of cleanliness and also generalisation I
might as well VC it.
This refactor removes a lot of the 'training wheels' that doom
provides (i.e. no modeline, bindings, etc). Instead, I defined my own
modules and systems to help with those tasks. I am now using the default
emacs modeline, customised to my liking, as well as the default scratch
buffer as my startup page.
This basically allows me to have a finer degree of control over what my
Emacs is doing, which is great as I can remove redundant pieces that I
don't use.
Basically, instead of generating files at every save on Emacs, just load
them via org-babel-load-file. This means that I can rely on those
functions to compile and manage org file to elisp file conversions. This
happens at first run time, and will not compile org files to el files if
there have been no changes to the org files.