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

[Rainer Stengele <rainer.stengele@diplan.de>]

Am 22.07.2010 09:47, schrieb Carsten Dominik:
> 
> 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!
> 
> Indeed, this looks wrong.
> 
> Unfortunately I don't have time to look at this before my vacation (starting tomorrow....) :(
> Please remind me when I get back.
> 
> - Carsten
> 

Hi Carsten,

this is still open, I just tested. I feel like this is a near to "major" bug
because it will simply "vary" your (work) time calculation if you choose different maxlevels.

- Rainer