init.org Without org-mode26 Jun 2014, by Artur Malabarba.
About the Blog post series
- init.org Without org-mode
- How I blog: One year of posts in a single org file
When I decided to share my limited wisdom, I realized I’d need something better than a 4-year-old, thrown together, init file. The words “init dot org” had crossed my ears through one of Sacha Chua’s previous videos; however, due to 63m of water above my head, internet searches weren’t quite operating at top efficiency.
Without a second thought, and armed with nothing but its name (init.org), I took to writing —I thought at the moment— the simplest way of implementing such a feature.
Once back within the range of cell towers, a quick search revealed it could have been slightly shorter.
Nonetheless, I stuck with my guns and kept the first version. Primarily for stubbornness, but also a few other reasons:
- Fine grained control
- I can choose exactly what gets
evaluated. In this case, anything inside the
init.elheader. This is important because this blog is my init file, and I don’t want to evaluate everything I post.
- Lots of messaging
- It calls
messageon each header it finds (up to a configurable level). Whenever something goes wrong, forget about restarting with
--debug-init, the messages buffer tells me exactly where it happened.
- It doesn’t
- This might sound silly, but that inconspicuous line forms one of the most time-consuming statements you could possibly write. I’d challenge anyone to find a 14-character statement that takes longer than that (other than an empty loop or a sleep command, of course).