Now showing
Emacs: custom Org clock report for my coaching
About this film
In this video, I demonstrate the custom code I have to generate Org clock reports for my coaching sessions. The idea is to use the DEADLINE and CLOSED timestamps of each task to calculate their elapsed time. This way, I do not need to manually clock in to the task and then clock out of it. It is easier to not have that overhead and not to duplicate the data that is already embedded in the aforementioned timestamps. The custom command I use will prompt me for the name of a person and the date since when to collect meetings. It will then put all the retrieved data in a new buffer and calcucate the results in a neat time table. This new buffer is not related to the underlying file I used to gather the data from: it is strictly used for reporting. My file stays free from all the extra noise. I thus use this method to do my billing and accounting. As I show in the video, my coach.org file is simple. Each meeting is a top-level heading. The text of the heading includes the name of the person and a description on what the meeting is about. It looks like this: #+todo: COACH(k) | DONE(d!) CANCEL(c@) * DONE Protesilaos Emacs deep dive CLOSED: [2024-12-10 Tue 14:45] DEADLINE: <2024-12-10 Tue…
Directors & creators
Protesilaos Stavrou
More from this pool