From mboxrd@z Thu Jan 1 00:00:00 1970 From: jmcbray@carcosa.net (Jason F. McBrayer) Subject: Re: Clocktable from multiple files? Date: Thu, 13 Sep 2007 10:01:17 -0400 Message-ID: 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 1IVpG0-0002iz-7W for emacs-orgmode@gnu.org; Thu, 13 Sep 2007 10:01:24 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IVpFz-0002gv-8l for emacs-orgmode@gnu.org; Thu, 13 Sep 2007 10:01:23 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IVpFz-0002gg-4G for emacs-orgmode@gnu.org; Thu, 13 Sep 2007 10:01:23 -0400 Received: from cdptpa-omtalb.mail.rr.com ([75.180.132.120]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IVpFy-0006D3-Hy for emacs-orgmode@gnu.org; Thu, 13 Sep 2007 10:01:22 -0400 In-Reply-To: <05bd06e8cce5d8c8ccdddeebf980da98@science.uva.nl> (Carsten Dominik's message of "Thu, 13 Sep 2007 07:10:36 +0200") 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: Carsten Dominik Cc: emacs-orgmode@gnu.org Carsten Dominik writes: > In fact, maybe the whole clocking stuff needs an overhaul at some > point, but right now I don't have time to do it. I not sure in what > direction to take this. Maybe create a timeclock - compatible list > from scanning the agenda buffers? I still think that collecting the > CLOCK entries in the outline does make a lot of sense. The clock > table was a quick hack I once did, but apparently not really though > through very well. I can't volunteer to write anything at this point, but I do have some comments. I think accumulating CLOCK entries in the outline is The Right Thing. It keeps the times with the tasks, and so forth, and clocking in and out of tasks is really convenient. What we're lacking right now are flexible-enough ways of dealing with the information those entries represent. Right now, the clock table does everything I really need to do, but not everything I would like to be able to do. Here are some things that any future org-clock.el or similar ought to be able to handle: 1. Including CLOCK entries from all org-agenda-files in its summaries 2. Including CLOCK entries from archive files associated with files used to construct its summaries. Right now I can't archive completed projects because of the need to include them and their tasks in monthly reports, for example. 3. Conversely, limiting summaries to only a subtree (having a clock table per project, for example). I don't need this right now, but someone consulting or freelancing for several clients probably would. Maybe someone will get inspired by this :) -- +-----------------------------------------------------------+ | Jason F. McBrayer jmcbray@carcosa.net | | If someone conquers a thousand times a thousand others in | | battle, and someone else conquers himself, the latter one | | is the greatest of all conquerors. --- The Dhammapada |