emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Mikhail Skorzhisnkii <mskorzhinskiy@eml.cc>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: emacs-orgmode@gnu.org
Subject: Re: Clock tables and two ways to categorize tasks
Date: Thu, 19 Nov 2020 15:47:46 +0100	[thread overview]
Message-ID: <87v9e12yjx.fsf@eml.cc> (raw)
In-Reply-To: <87tutljzxo.fsf@mbork.pl>

Hi Marcin,

I tried to solve this issue for myself. My first attempt to solve 
it was to understand which tags are interesting and then make a 
template with as many tables as there were interesting tag 
combinations. But then I faced another problem: sometimes I am 
using different set of tags and templates don't work as good as 
they could.

To mitigate that problem, I've tried different approach. I made a 
small package that generates me reports for past week or past 
month. It's working for me, but there are a lot of rough edges 
around it. Basically it collects headers with clocks, copies them 
to separate file, rearrange them and generate clock tables. You 
can try it here:


Another way would be to write your own clock table sorter. See 
this post on reddit:


And just for future references, in case Reddit someday will go 

  Code from /u/jp5ear: 
  Org-mode manual: https://orgmode.org/manual/The-clock-table.html 
  (see :formatter parameter)

Mikhail Skorzhinskii

Marcin Borkowski <mbork@mbork.pl> writes:

> Hi all,
> here's the problem I'd like to solve.  I clock various tasks, 
> and then
> generate a clock table.  So far, so good.  But now I'd like to 
> know
> better where my time goes.  Most tasks I do have a few similar
> components: discussion/research, writing code, testing, etc.  I 
> thought
> that I could create subheadlines under each of the tasks and 
> give them
> tags like :discuss:, :code:, :test:, :debug: and so on.  (Not 
> very
> convenient, but doable, maybe with a bit of Elisp to automate 
> the
> process.)
> Now, I'd like to prepare two clock tables: one where I see how 
> much time
> every task took, and one where I can see how much time I spent 
> coding,
> testing, debugging, emailing etc.  I can see in the docs that 
> there is
> the ~:match~ option, but if I understand it correctly, it can 
> only
> restrict the table to /one/ tag, so I'd need to have as many 
> tables as
> I have tags - not optimal.
> Any ideas?  Should I use something else than tags for that?
> TIA,

Mikhail Skorzhinskii

  reply	other threads:[~2020-11-19 14:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19 12:25 Clock tables and two ways to categorize tasks Marcin Borkowski
2020-11-19 14:47 ` Mikhail Skorzhisnkii [this message]
2020-11-19 14:52 ` Tim Cross
2020-11-20  8:20 ` Leo Okawa Ericson
2020-11-22  5:55   ` Kristian Grönberg
2020-11-22  7:06     ` Tim Cross
2020-11-22 18:16     ` Jean Louis
2020-11-22 21:28       ` Marcin Borkowski
2020-11-22 22:11         ` Jean Louis
  -- strict thread matches above, loose matches on Subject: below --
2020-11-20  0:37 Bala Ramadurai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v9e12yjx.fsf@eml.cc \
    --to=mskorzhinskiy@eml.cc \
    --cc=emacs-orgmode@gnu.org \
    --cc=mbork@mbork.pl \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).