dotfiles

Heh, I recently did a "clean sweep" of my .emacs files (inspired by the new support for `$XDG_CONFIG_HOME/config/emacs/init.el` in 27.1) and something like 90% of it was workarounds (some dating back to the late 1990s, for example a "vertical-motion-fix" for something that was fixed in emacs 19.29) I definitely recommend doing some form of "dotfile bankruptcy" every 20 years or so :-) (I also ended up doing a crude "load-file-literate" so that now most of my elisp is actually markdown, inspired by https://github.com/skx/dotfiles )

I keep meaning to experiment with bable/tangle in Emacs. I setup a simple literate configuration of my init file via markdown, which worked out really well, but doing it "properly" in org-mode would be a nice evolution. With markdown I just search for code-blocks, write them all sequentially to a temporary buffer and evaluate once done. So it is very simplistic, but also being able to write and group things is useful: https://github.com/skx/dotfiles/blob/master/.emacs.d/init.md

You need to evaluate the lisp at the bottom of the file, so that `M-x new-day`, `M-x today` and the other stuff gets loaded. I've got a bit of code in my init-files that does that automatically, that's linked to in the readme. But as a quick alternative you can scroll down to the end, to the line that starts: "(defun new-day" Select that line, and all the way down to the line that reads "(require 'ob-org)", and then run "M-x eval-region". That will evaluate the region and make the two new commands available. Otherwise copy and paste the lisp from here into your emacs init file, and reload everything: https://github.com/skx/dotfiles/blob/master/.emacs.d/init.md... That will cause anything named `skx-startblock` to be evaluated automatically from an org-file on-load, and will also run the contents of `skx-saveblock` before saving any

I wrote mine in markdown, with comments and explanation: https://github.com/skx/dotfiles/blob/master/.emacs.d/init.md When emacs launches a simple `~.emacs.d/init.el` file parses that markdown, building up all the code-sections into a temporary buffer, then evaluates them. Pretty neat.

If you like that you might enjoy my literate emacs setup: https://github.com/skx/dotfiles/blob/master/.emacs.d/init.md Not remotely as well-documented, but still understandable to the novice I hope.

I do that in my dotfiles too: The main include: https://github.com/skx/dotfiles/blob/master/.bashrc The actual dotfiles: https://github.com/skx/dotfiles/ (People usually copy the literate emacs configuration ..)

I've used org-mode with inline code a few times now, and it is terribly expressive and useful when you want to show reports with "live" results in them, etc. That said when it came to formatting my Emacs init file, with descriptions, and justifications, I chose to use markdown: https://github.com/skx/dotfiles/blob/master/.emacs.d/init.md Markdown allows text, and code, to be mixed, and while there is no inline expansion support or other neat features it is minimal enough that it was painless to write and process.

If you enjoy this style of literate documentation, then you might enjoy my personal Emacs configuration too (it is smaller). The following should be placed in ~/.emacs/init.el: https://github.com/skx/dotfiles/blob/master/.emacs.d/init.el That reads and parses the following Markdown file, which contains documentation for humans and indented code-blocks which are executed by Emacs: https://github.com/skx/dotfiles/blob/master/.emacs.d/init.md

If you write a small pre-processor (simple to do) you can store your emacs configuration file in a markdown file - allowing you to document all the settings neatly. As I was reading this piece I was imagining that is what the author had done, as it is what I did too: https://github.com/skx/dotfiles/blob/master/.emacs.d/init.md

You might enjoy this then: https://github.com/skx/dotfiles/tree/master/.emacs.d In there you'll find ~/.emacs/init.el which parses ~/.emacs/init.md which is a markdown file containing both documentation and executable Lisp. There are other files in separate directories/packages, but I like the idea of placing everything in one readable file: https://github.com/skx/dotfiles/blob/master/.emacs.d/init.md

My actual~/.bash_profile file is very minimal, it just sources each file in ~/.bash/ in turn. You can see the organized contents of that directory here: https://github.com/skx/dotfiles/tree/master/.bash/

Very little. I just source a small number of real configuration files from the ~/.bash/ directory: https://github.com/skx/dotfiles/tree/master/.bash