dotDOOM
Table of Contents
This looks better on the website.
1. What?
This is actually a doom-emacs private module. I was feeling rather whimsical.
1.1. Configuration
This is documented here.
1.2. Packages
I also document the packages I use in a separately here.
2. Why?
My Dotfiles repo, managed with the brilliant dotgit, was getting rather overwhelmed
with emacs commits. Also managing snippets with dotgit was not exactly
pleasant, since each symlink needed to be listed in the filelist.
2.1. Who?
I'm Rohit Goswami (or HaoZeke, or rg0swami), and well, if you need to know more about why you might want to use my work, check my site, or any of the other sites I manage, or even my publications or my code.
3. How?
Well it just goes where doom expects config files.
# Honestly, this should be $HOME/.config
git clone git@github.com:HaoZeke/dotdoom $HOME/.config/doom
4. Maintenance
The canonical configuration sources are config.org and packages.org.
Run scripts/tangle-doom-config after editing them; it regenerates the ignored
config.el and the tracked packages.el from those Org sources.
Local helper modules live under local/rg-*.el with matching ERT tests. The
encrypted local/private.el.gpg holds host-local paths and private custom state.
The docs/ directory is the tracked static site output for this repo; keep
docs/CNAME and docs/keybase.txt with it. The reveal/rjs/ tree is vendored
reveal.js for Org reveal exports, and reveal/extras/ contains local
presentation CSS.
5. Config
Doom reads init.el, the generated config.el, and the tracked packages.el.
The maintained commentary lives in config.org and packages.org.
6. License
It is a personal configuration. So I guess the MIT license will do for now.