emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alexander Adolf <alexander.adolf@condition-alpha.com>
To: Carlo Tambuatco <oraclmaster@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Support for simultaneous running clocks?
Date: Fri, 24 Jul 2020 13:59:22 +0200	[thread overview]
Message-ID: <65bb73d200b3b395e1ab36af122d8531@condition-alpha.com> (raw)
In-Reply-To: <CAJb92EyPM+kYCfd5zzz9ySDSq74H4pviwbwo75shD2Eeg3P0EA@mail.gmail.com>

Hello Carlo, Org Devs,

Carlo Tambuatco <oraclmaster@gmail.com> writes:

> I don't know if anyone has suggested or is working on the ability for
> org mode to keep track of multiple running clocks simultaneously. I'd
> like the ability to keep track of, for example, how long something
> takes to compile while I keep track of how long I am working on some
> other project task at the same time.

I have worked with quite a couple or work tracking tools, Org being one
of them (albeit my favourite one). I learnt that running multiple clocks
in parallel was an idea that didn't work out for me. In reality, I'm
only ever doing one thing at a time [1]. If I want to bill that one
thing multiple times, I clock it once, and just duplicate the time
clocked to "the other" project(s). Or, with Org an elisp support, you
can create a "magic timer", whose recorded times will be automatically
copied to all "linked" projects. If I ran multiple clocks at the same
time, I would - more often than not - forget to start or stop one of
them, messing up my accounting. Hence, my baseline is "run a single
clock only, tracking what I'm doing, and do any doubling-up-magic in the

Also, to gauge build times, it might seem more promising to make the
bench marking part of the build process itself ("Build took ...")?

[1] https://hbr.org/2010/12/you-cant-multi-task-so-stop-tr

Just my two cents anyway.



  parent reply	other threads:[~2020-07-24 11:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-18 15:57 Support for simultaneous running clocks? Carlo Tambuatco
2020-07-19 13:08 ` stardiviner
2020-07-24 11:59 ` Alexander Adolf [this message]
2020-09-04 17:14 ` Bastien
2020-09-05  5:27   ` stardiviner
2020-09-10 20:48   ` TRS-80
2020-09-10 22:15     ` Samuel Wales
2020-09-12  6:16       ` Michael Welle
2020-09-23 14:34         ` stardiviner

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=65bb73d200b3b395e1ab36af122d8531@condition-alpha.com \
    --to=alexander.adolf@condition-alpha.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=oraclmaster@gmail.com \


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