emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marcin Borkowski <mbork@mbork.pl>
To: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Clock tables and two ways to categorize tasks
Date: Thu, 19 Nov 2020 13:25:55 +0100	[thread overview]
Message-ID: <87tutljzxo.fsf@mbork.pl> (raw)

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

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?


Marcin Borkowski

             reply	other threads:[~2020-11-19 12:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19 12:25 Marcin Borkowski [this message]
2020-11-19 14:47 ` Clock tables and two ways to categorize tasks Mikhail Skorzhisnkii
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=87tutljzxo.fsf@mbork.pl \
    --to=mbork@mbork.pl \
    --cc=emacs-orgmode@gnu.org \


* 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).