Announcing `work-log'
All of you played Doom. Some of you know that it was programmed by John Carmack. Few of you might be aware of .plan files he posted even before the term `blog' was invented. And I find the format used in those files to be clean, minimalistic, and fitting my own issue-tracking habbits.
The format is simple:
* entry was completed on that day
+ entry was completed on a later day
- entry was decided against on a later day
2009-05-02 advertise work-log.el 2009-04-09 + hack "log-mode": start with implementing `C-x 4 a' (change-log-mode) + fix jabber-el's "Idle" status 2008-12-24 + kill the bad guys - save the world the princess?
Whichever log format is used, log file will grow with time. In three months I had a long file with unfinished tasks being scattered and tiresome to find. I wanted to make them visually distinguishable from completed/rejected. Thus work-log.el was born.
While implementing emacs mode, I've made a minor change to Carmack's format, moving unfinished tasks to the top of day record. Open items are what I care about, and they shouldn't be hidden under historical luggage.
# -*- work-log -*- 2009-05-02 advertise work-log.el * debug battery-dzen.pl (division by "ok" is... well, not ok) 2009-04-09 + hack "log-mode": start with implementing `C-x 4 a' (change-log-mode) + fix jabber-el's "Idle" status 2008-12-24 + save the bad guys + kill the princess - save the world
Key bindings: C-c e add new entry C-c h, C-c s hide/show resolved entries C-c n, C-c p go to next/previous date
git clone git://github.com/vvv/work-log.git
Have fun!