From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Clocktable from multiple files? Date: Wed, 19 Sep 2007 21:26:30 +0200 Message-ID: References: <05bd06e8cce5d8c8ccdddeebf980da98@science.uva.nl> Mime-Version: 1.0 (Apple Message framework v624) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IY6N5-0007ae-FN for emacs-orgmode@gnu.org; Wed, 19 Sep 2007 16:42:07 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IY6N4-0007aA-J5 for emacs-orgmode@gnu.org; Wed, 19 Sep 2007 16:42:06 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IY6N4-0007a3-Eg for emacs-orgmode@gnu.org; Wed, 19 Sep 2007 16:42:06 -0400 Received: from korteweg.uva.nl ([146.50.98.70]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IY6N4-0002Af-2E for emacs-orgmode@gnu.org; Wed, 19 Sep 2007 16:42:06 -0400 In-Reply-To: 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: "Jason F. McBrayer" Cc: emacs-orgmode@gnu.org On Sep 13, 2007, at 16:01, Jason F. McBrayer wrote: > 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 This one is really needed, yes. Will add this soon. > 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. I am not so sure about this. The whole idea about archiving is that this project should no longer be used in all the list compilation by org-mode. So my feeling would be that you should keep that tree in your work file until you no longer need it. Also, with some files having multiple archive files, this gets messy. > 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. Indeed, also very useful. This will happen. - Carsten