Re: clocktable: maximum level 0 does not only avoid listing items but also does not calculate items

[Bernt Hansen <bernt@norang.ca>]

Carsten Dominik <carsten.dominik@gmail.com> 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