From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Clocktable from multiple files? Date: Thu, 13 Sep 2007 19:07:20 +0200 Message-ID: <87hclyo5o7.fsf@bzg.ath.cx> References: <05bd06e8cce5d8c8ccdddeebf980da98@science.uva.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IVsAC-0003m8-HZ for emacs-orgmode@gnu.org; Thu, 13 Sep 2007 13:07:36 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IVsA8-0003kf-Pt for emacs-orgmode@gnu.org; Thu, 13 Sep 2007 13:07:36 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IVsA8-0003ka-NO for emacs-orgmode@gnu.org; Thu, 13 Sep 2007 13:07:32 -0400 Received: from ug-out-1314.google.com ([66.249.92.172]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IVsA8-0002dr-8n for emacs-orgmode@gnu.org; Thu, 13 Sep 2007 13:07:32 -0400 Received: by ug-out-1314.google.com with SMTP id m4so463798uge for ; Thu, 13 Sep 2007 10:07:30 -0700 (PDT) In-Reply-To: (Jason F. McBrayer's message of "Thu, 13 Sep 2007 10:01:17 -0400") 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: emacs-orgmode@gnu.org jmcbray@carcosa.net (Jason F. McBrayer) writes: > I can't volunteer to write anything at this point, but I do have some > comments. Same here. > I think accumulating CLOCK entries in the outline is The Right Thing. I think it's okay, but I guess lots of people (including me) don't care about the detailed clocking history - I just need to know how much time I spent on a task. So a simple :CLOCK: property might be an alternative way to keep track of all the clocking stuff. We could even refine this and have something like a :CLOCKED-IN: property for tasks that last more than the duration of an Emacs session (which equals the lifespan of an Org buffer :) I would also make it possible to merge all the CLOCK: lines into a single :CLOCK: property. Then what we need is to make `org-clock-sum' and `org-clock-display' handle the new :CLOCK: property so that the :org-clock-minutes property is uptodate in headlines properties. For multi-files timeclock reports, I guess collecting :org-clock-minutes from headlines is the easy way... > Maybe someone will get inspired by this :) Sure! -- Bastien