I think I started getting interested in
org-mode in 20071. I definitely was making serious attempts to integrate it into my workflow by 2010. By 2016 it became my primary tool. By primary tool, I mean that most of my daily work is either done from within or at least I’ve probably written down something about what I’ve done in
Early on, maybe 2009 I found Bernt Hansens Organize you life in plain text! guide, it was, and still is an amazing document. I found the title so inspiring. At the time I was heavily focused on GTD and I recall setting up Emacs specifically for managing tasks using org agenda. Unfortunately, being treated like a standalone app, I couldn’t make it stick in my workflow. I was uncomfortable without modal editing and vi keybindings. Constantly pasting and editing org files in the background with vim just wasn’t efficient. I drifted into some scripts to manage todos from the command line2 and then to the opposite end of the spectrum with Evernote3.
In 2013 I was traveling a lot, meeting many different people and taking copious notes about challenges people were facing and what they wanted to achieve. The Evernote service was pretty OK, but I hated the thought that my precious notes were in someone else’s locker. So, when I’m running on Linux in some place with low or no Internet, power etc …. And wanting to work on my notes what am I to do? Well, Nixnote4 was ok. But it would crash and get slow, and when things blew up I was short of stranded until I got it fixed. I longed for the simplicity of plain text, where I could just use vim when things were burning around me.
Org-mode remained in the back of my mind and around 2015 I made an effort to migrate my notes into
org-mode. I got evil mode working pretty well and managed to transition from Evernote.
By 2016 I found Spacemacs5. This was a huge accelerator. Evil mode worked out of the box, plus
cfengine-mode in Emacs was significantly better than
vim_cf3 6. Not only did it provide highlighting, it also provided function prototypes as I typed via eldoc, syntax checking via fly check, and projectile made it easy to test a full policy set. Things quickly progressed from there as I kept finding more ways to avoid leaving
org-mode (ok, yeah, it’s Emacs, but in my head
org-mode is the focus) making it easier to wrangle text and weave things into my notes.
I started making presentations in
org-mode, with the help of org-reveal exporting to reveal.js7.
Next I added email via
mu4e8. Which really facilitated authoring email responses in
org-mode. It became easy to email notes to colleagues and construct highly technical responses. I could see the potential for not organizing my life in plain text, but living my work life in plain text.
I started making more use of
org-babel and cobbled together
ob-cfengine39 which let me author and run snippets of CFEngine policy directly in my notes. Along this path I found Howard Abrams post about literate DevOps10 which was very similar to what I was doing. He echos many of my values in his post.
So, I could get an email with a question, select the interesting part of the email that I wanted to respond to and trigger a capture bringing that text with a link that I could follow back to that email right into
org-mode. I could author and run code blocks illustrating something and respond without ever breaking stride.
It was easy to create detailed logs investing something with a trail of src blocks with output along the way. I could easily take that text and export it to the bespoke markup for a ticketing system (Jira, with
ox-jira 11before it transitioned to markdown, and Markdown after). I was even using
org-jira 12 to directly interface with the ticketing system, posting comments directly from the comfort of
By 2021 I had run into various performance issues that really centered around large files. Large files that have high churn (eg. As the result of large results from src blocks that are sometimes rerun many times) made my environment slow and sent me in search of new strategies which is when I came across org-roam13.
Org-roam uses the zettelkasten method of organization. It provides some functions that facilitate a methodology built around many smaller interlinked files. I started making heavy use of
org-roam-dailies-capture which brings me to how I org in 2023.
Seems right, Linux Journal had an article about
org-modein 2007. https://www.linuxjournal.com/article/9116 ↩︎
I had written my own todo manager based off of Tom Limoncellies Cycle from Time Management for Systems Administrators and I had been trying out todo.txt (which is still around and has a nice little Android app) http://todotxt.org/. ↩︎
I loved the Evernote motto, remember everything
At least in 2023 Evernote’s motto seems to be “Tame your work, organize your life Remember everything and tackle any project with your notes, tasks, and schedule all in one place.” https://evernote.com/ ↩︎
Nixnote is a desktop client for Evernote that runs on Linux and Windows http://www.nixnote.org/ ↩︎
A community-driven Emacs distribution. The best editor is neither Emacs nor Vim, it’s Emacs and Vim! https://www.spacemacs.org/ ↩︎
Vim support for syntax highlighting, abbreviations, code tidying and templates made by Neil Watson. https://github.com/neilhwatson/vim_cf3 ↩︎
Reveal.js is an html presentation framework. It produces nice looking html slides and has features like speaker-notes and even live code execution. https://revealjs.com/ ↩︎
mu4e is an email client for Emacs built on top of the
musearch engine. It’s optimized for quickly processing large amounts of email. It operates on mail directories, so you need to sync your email locally with something like isync https://www.djcbsoftware.nl/code/mu/mu4e/index.html ↩︎
My first emacs package, I gave it to myself for my 36th birthday. I figure that it saved me at least 36 seconds for every CFEngine example snippet that I write and it’s definitely paid for itself. I don’t make many changes to it, Diego Zamboni has contributed some nice features. https://github.com/nickanderson/ob-cfengine3 ↩︎
I really dislike the term DevOps but I found Howard’s post reached in the direction I was headed. It’s a great resource. https://howardism.org/Technical/Emacs/literate-devops.html ↩︎
ox-jiraexports to the Jira wiki markup. Plausibly only useful these days if you are running the Data Center edition. Jira Server is dead, and Jira Cloud dropped support for their old wiki markup. Now they support a very small subset of Markdown. I much preferred the old support (but only because I had
org-modeto export to it). Now for Jira I just export to markdown and paste into their web form. https://github.com/stig/ox-jira.el ↩︎
Interact with Jira issues without leaving
org-modeat all! This was pretty darn neat, sadly it stopped working on Jira server at some point and I have yet to try to get it working with Jira cloud. https://github.com/ahungry/org-jira ↩︎
Org-roam is a tool for networked thought. It reproduces some of Roam Research’s key features within Org-mode. https://www.orgroam.com/ ↩︎