From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Feature idea: Automatic clocking Date: Sun, 23 Aug 2009 12:30:21 +0800 Message-ID: <873a7j17aa.fsf@bzg.ath.cx> References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MfBHQ-0008BA-T0 for emacs-orgmode@gnu.org; Sun, 23 Aug 2009 07:30:36 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MfBHM-000851-C9 for emacs-orgmode@gnu.org; Sun, 23 Aug 2009 07:30:36 -0400 Received: from [199.232.76.173] (port=47740 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MfBHM-00084t-6D for emacs-orgmode@gnu.org; Sun, 23 Aug 2009 07:30:32 -0400 Received: from mail-ew0-f211.google.com ([209.85.219.211]:57025) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MfBHL-0002s1-QQ for emacs-orgmode@gnu.org; Sun, 23 Aug 2009 07:30:31 -0400 Received: by ewy7 with SMTP id 7so1711351ewy.31 for ; Sun, 23 Aug 2009 04:30:31 -0700 (PDT) In-Reply-To: (PT's message of "Fri, 21 Aug 2009 18:35:27 +0000 (UTC)") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: PT Cc: emacs-orgmode@gnu.org 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