I do this as well! I have this repo [0] at ~/cfg, then I symlink what I need [1] as an init script. My end goal is to be able to run a single script and get everything [2] set up on a new machine (I change machines somewhat frequently and I got the manual process to under 45 minutes, so there's room for improvement). More on setting up Macs [3].
There is also GNU Stow [4] that does something similar, and probably better.
0: https://github.com/andreis/cfg
1: https://github.com/andreis/cfg/blob/master/init.sh#L64-L69
2: brew and brew cask, dotfiles ofc, and a _lot_ of system settings on mac os can be changed via the CLI, see
3: https://github.com/iCHAIT/awesome-macOS#setup
4: http://brandon.invergo.net/news/2012-05-26-using-gnu-stow-to...
Re:'Using Emacs' Series
by frumiousirc on Saturday July 29, 2017 @08:09AM
(#14880794)
I used to do it that way. I've switched to `vcsh` to let me keep various files directly in my ~/ directory in various different git repos without needing a ~/.git/ marking the whole thing as a working directory.
So each time you launch emacs you have to point it to your init file?
- .emacs - which defines my config dir and loads everything in there
- my own config dir (called .emacs.conf), in which I have lots of .el files with specific configurations
Emacs packages still write by default to .emacs.d, and this way I don't have to care about any of that when moving between machines, because my configuration and Emacs's ongoing state are separate.
To be honest, though, I'll probably be migrating into a single-file literate solution soon, which will render my own config directory unnecessary.