emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bastienguerry@googlemail.com>
To: PT <spamfilteraccount@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Feature idea: Automatic clocking
Date: Sun, 23 Aug 2009 12:30:21 +0800	[thread overview]
Message-ID: <873a7j17aa.fsf@bzg.ath.cx> (raw)
In-Reply-To: <loom.20090821T202641-395@post.gmane.org> (PT's message of "Fri, 21 Aug 2009 18:35:27 +0000 (UTC)")

Here is another approach to this auto-clocking question.

Maybe what you really want to track is not how much time you spend on a
specific task but rather how you distribute your time over the tasks.

In this case, you don't need to explicitely clock in and out.  You can
act as if a clock was always running¹ and then you register any action
you take on your Org file.  "Working on this X task" would just be an
action among others like "switching task X from TODO state to NEXT",
"closing task X", "Archiving task X", "Moving task X under Tree T", 
etc.

Thus, instead of automating the aggregation of clocked-in tasks, you
consider yourself always clocked in and you automate the logging of
stuff you do (from which you can extract clock information later.)

I guess this idea come closer to what Samuel had in mind when he talked
about "profiling".

¹ Actually, astronomers from this list could tell us that the universe
  is such a running clock in itself :)

-- 
 Bastien

  parent reply	other threads:[~2009-08-23 11:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-21 18:35 Feature idea: Automatic clocking PT
2009-08-21 19:26 ` Bernt Hansen
2009-08-23 10:38   ` Carsten Dominik
2009-08-21 23:15 ` Samuel Wales
2009-08-23  4:30 ` Bastien [this message]
     [not found] <DICKENSGQnnJOxa3bb20000006e@dickens.campus.up.edu>
2009-08-22 16:18 ` Nuxoll, Andrew

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=873a7j17aa.fsf@bzg.ath.cx \
    --to=bastienguerry@googlemail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=spamfilteraccount@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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