From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: Re: clocktable: maximum level 0 does not only avoid listing items but also does not calculate items Date: Sat, 30 Oct 2010 12:18:42 -0400 Message-ID: <87pqurodr1.fsf@gollum.intra.norang.ca> References: <4C47F049.6060101@diplan.de> <231F0792-669F-49D2-976A-392EFA2C9EB9@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from [140.186.70.92] (port=54249 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PCE8s-0002oJ-1H for emacs-orgmode@gnu.org; Sat, 30 Oct 2010 12:18:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PCE8r-0000t2-0G for emacs-orgmode@gnu.org; Sat, 30 Oct 2010 12:18:53 -0400 Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:56595) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PCE8q-0000sc-Ut for emacs-orgmode@gnu.org; Sat, 30 Oct 2010 12:18:52 -0400 In-Reply-To: <231F0792-669F-49D2-976A-392EFA2C9EB9@gmail.com> (Carsten Dominik's message of "Tue, 26 Oct 2010 13:30:46 +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: org-mode List , Rainer Stengele Carsten Dominik writes: > Hi Rainer, hi Bernt, > > On Jul 22, 2010, at 9:16 AM, Rainer Stengele wrote: > >> #+BEGIN: clocktable :maxlevel 0 :scope ("file1.org" "file2") >> :timestamp t :tstart "<2010-05-01 Sa 00:00>" :tend "<2010-07-31 Sa >> 23:55>" >> Clock summary at [2010-07-22 Do 09:11] >> >> | File | L | Timestamp | Headline | Time | >> |------+---+-----------+--------------+----------| >> | | | Timestamp | *Total time* | *232:17* | >> |------+---+-----------+--------------+----------| >> #+END: >> >> >> I would like to get the same results! >> Is ":maxlevel 0" intended to not include the sublevel clocks? > > I think I have finally fixed this bug. Please verify. > > Bernt, I made a change to clock tables which I think I understand. > But can you please watch out for inconsistencies with the newest > version? Maybe run some tests with old and new version, to make sure > clock tables deliver the same results? > > Thanks! > > - Carsten Hi Carsten, I've been at a commit before the clock tables change until today. I've update to the current master and reviewed my agenda clock table results for every day in October and the results are identical for me before and after this change. Thanks, Bernt