From: Carsten Dominik <carsten.dominik@gmail.com>
To: Rainer Stengele <rainer.stengele@diplan.de>
Cc: Bernt Hansen <bernt@norang.ca>, org-mode List <emacs-orgmode@gnu.org>
Subject: Re: clocktable: maximum level 0 does not only avoid listing items but also does not calculate items
Date: Tue, 26 Oct 2010 17:52:30 +0200 [thread overview]
Message-ID: <17D87A22-AF39-43F2-AA5F-58115D19EB12@gmail.com> (raw)
In-Reply-To: <4CC6DD46.3050507@diplan.de>
On Oct 26, 2010, at 3:53 PM, Rainer Stengele wrote:
> Am 26.10.2010 13:30, schrieb Carsten Dominik:
>> Hi Rainer, hi Bernt,
>>
>> On Jul 22, 2010, at 9:16 AM, Rainer Stengele wrote:
>>
>>> Am 21.07.2010 16:24, schrieb Carsten Dominik:
>>>>
>>>> On Jul 13, 2010, at 11:21 AM, Rainer Stengele wrote:
>>>>
>>>>> Hi all!
>>>>>
>>>>> lately I use the marvelous clocktables a lot...
>>>>>
>>>>> For toplevel clocktables which just sum up "all" I use
>>>>> ":maxlevel 0"
>>>>>
>>>>> The manual reads
>>>>>
>>>>> :maxlevel Maximum level depth to which times are listed in
>>>>> the table.
>>>>>
>>>>> which I misunderstood.
>>>>> I understood: an unlisted item does not mean that its time is
>>>>> not added!
>>>>> But it looks like ":maxlevel 0" does not add everything up.
>>>>
>>>>
>>>> I cannot reproduce this, :maxlevel 0 works for me.
>>>>
>>>>>
>>>>> Ok, maybe the manual is a bit misleading here.
>>>>>
>>>>>
>>>>>
>>>>> How can I get a clocktable without any details which simply adds
>>>>> up everything in the scope?
>>>>>
>>>>> BTW, the ":stepskip0" parameter does not seem to be included in
>>>>> the manual.
>>>>
>>>> It is in the manual.
>>>>
>>>> - Carsten
>>>>>
>>>>>
>>>>> Rainer
>>>>>
>>>>>
>>>>>
>>>
>>>
>>> Carsten,
>>>
>>> maybe I misunderstood.
>>>
>>>
>>> 1. Without maxlevbel I get I get
>>>
>>> #+BEGIN: clocktable :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:07]
>>>
>>> | File | L | Timestamp | Headline
>>> | Time | | |
>>> |-------------------+---+---------------------+----------------
>>> +----------+--------+--------|
>>> | | | Timestamp | *Total time* |
>>> *327:51* | | |
>>> ...
>>>
>>>
>>>
>>> with :maxlevel 0 I get
>>>
>>>
>>> #+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 checked and found:
>
> - clocktable sums are resulting in identical values, independant of
> the ":maxlevel" level
> - without ":maxlevel" parameter some tables now give slightly
> different results than in the past, some give identical results
> * I hope the new results are correct, but I did not have time to
> check in detail
>
> Looks good, I will test further.
no, this did not look good.
I think I have found a bug, please pull again...
- Carsten
next prev parent reply other threads:[~2010-10-26 16:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 9:21 clocktable: maximum level 0 does not only avoid listing items but also does not calculate items Rainer Stengele
2010-07-21 14:24 ` Carsten Dominik
2010-07-22 7:16 ` Rainer Stengele
2010-07-22 7:47 ` Carsten Dominik
2010-10-07 8:41 ` Rainer Stengele
2010-10-26 11:30 ` Carsten Dominik
2010-10-26 13:53 ` Rainer Stengele
2010-10-26 14:27 ` Carsten Dominik
2010-10-26 15:52 ` Carsten Dominik [this message]
2010-10-26 22:55 ` Bernt Hansen
2010-10-27 7:01 ` Rainer Stengele
2010-10-30 16:18 ` Bernt Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17D87A22-AF39-43F2-AA5F-58115D19EB12@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=rainer.stengele@diplan.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).