Plain Text Todo lists
@workflow
I don't like having a separate app for managing TODO lists that doesn't fit in my workflow and whenever I try one, I don't stick to it. Using the "task" functionality of a digital agenda is a good option I reckon, but I have a tendency to not look in my agenda too much. Besides, I typically have multiple digital agendas (one for work, one for university, one personal) whereas I want a single place to keep track of my tasks. I typically end up scribbling TODOs on random pieces of paper, but that has some obvious disadvantages. I often lose them, don't have a single place with all information, and they are harder to reorganize. I'm aware of bullet journalling, but my personal history teaches me I tend to leave journals empty whenever I buy them, with the exception of the first few pages.
What works best for me is simply using plain text TODO lists with bullet points. It retains the simplicity of handwritten bullet points, but are easier to manage and organize.
Simple plain text TODOs are:
- human readable
- are usable with any text editor
- on any system (cross-platform)
- easy to sort with standard editing tools
- compatible with any productive framework such as "Getting Things Done"
- future proof
- easy to sync
- accessible from command line
- no fuss & task focused
Emacs' org-mode is the coolest thing ever and is also plain text, but it does force me to use Emacs and gives me a mild version of locked-in syndrome. Emacs is a bit of an exotic holiday for me. It's fun and I get to experience various approaches and ideas, but in the end I come back home to Vim with a fresh look. I know there are alternative apps and implementations for org mode, but once you've used it within the Emacs ecosystem, you don't really want some other rip-off.
This is of course all personal preference and mostly me working around my own deficiencies. But if you are like me, read along on a very simple way to manage plain text TODOs using Vim.
Setup & synchronization
Since we are working with plain text notes, all we need to get started is a text file.
Let's conveniently call it todo.txt.
At the end of the day I like seeing which tasks I've completed for review, so we can keep completed tasks in done.txt.
We also want to be able to switch machines and keep our TODOs.
I'm a heavy git user, but this is the one thing I prefer an app like Dropbox for.
We're going for simplicity here.
We're not going to be dealing with merge conflicts and the like.
Committing, pulling, pushing is overhead that is simply not needed here and also makes it difficult to manage your todo.txt on a cell phone (in case you really want to; I don't personally).
We'll end up with two files:
~/Dropbox/todo.txt and ~/Dropbox/done.txt.
An added benefit is that this path will be the same on any system where you install Dropbox.
Vim bindings
Visit todo.txt easily
Capture
Format (todo.txt)
It's handy to stick to a common convention for TODOs, which allows for better tool development. todo.txt prescribes a basic formatting of TODOs, but it provides everything I'd possibly need. There's also a Vim plugin that defines syntax highlighting, as well as mappings for basic operations on the TODO list.
Consider the following example from the README:
x (A) 2016-05-20 2016-04-30 measure space for +chapelShelving @chapel due:2016-05-30
From left to right:
- [Optional] Completion
- [Optional] Priority
- [Optional] Completion date
- [Optional] Creation Date (but must be specified if the completion date is specified)
- Todo description
- [Optional] Description tags
- +project tag
- @context tag
- arbitrary key:value pairs
The order of appearance is to a large degree flexible and is only limited by a few very simple rules, which are also explained in the README.
Thoughts on usage
My use of the project and context tags so far have been inconsistent, probably mainly because I don't yet follow a methodology such as GTD (where these tags come from). The project tag allows you to group TODOs in meaningful units and helps you avoid adding a whole project as a task. I guess the context allows you to group tasks that are more easily performed together, because switching contexts takes mental effort. I want to use project tags more consistently, but I find that I don't really need the context tag, as most my work is done on the computer anyways. Context switching on the computer is relatively cheap!
todo.txt puts emphasis on priority over due dates. Having a lot of overdue tasks is demotivating. You can avoid this by only putting tasks on the list that you actually intend to complete in the foreseeable future.
I have a need for a place where I can quickly write down project ideas for the future. I keep using my todo list for this, but this violates the basic tenets of the todo list: these entries tend to not get done, which makes sense as they actually aren't tasks.
TODO: sometimes I want to add some thoughts to a TODO. Is this possible?
this is really where todo.txt simplicity Because it does one thing only but does it well, it forces me to check function creep in my tools and workflow.
Capture functionality
One thing I really liked about org mode was working on a note or an email, have a thought, and immediately "capture" the thought in a log or TODO list with a link to the original file. I wanted this feature in Vim as well and record links in my TODO list. The following Vimscript snippet contains a binding to quickly jump to your TODO list, as well as a binding for a function that quickly captures an entry and sends it to your TODO list in the most basic todo.txt format. This works fine for me. Let me know if you have suggestions or improvements!
" ------------------ todo.txt ---------------------------
" extra bindings on top of todo.txt-vim
"
" \td go to todo.xt
" \tc todo capture (bit like Org capture)
let g:todo = "~/Dropbox/todo.txt"
nnoremap <Leader>td :execute ":e" todo<CR>
"nnoremap <Leader>tc :execute ".w >> " . todo
nnoremap <Leader>tc :Capture
command! -nargs=1 Capture :call CaptureWithLink("<args>")
" Drops todo with date, description and file link at bottom of todo.txt
:function! CaptureWithLink(description)
: echon '\r'
: execute 'redir >> ' . g:todo
: silent echomsg strftime('%Y-%m-%d') a:description fnameescape(expand('%:p')).':'.line('.')
: silent! redir END
: echom 'Captured in ' . g:todo
:endfunction