[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] Bug: org-dblock-update regression in case of :maxlevel 0 [9.0.5
From: |
Nicolas Goaziou |
Subject: |
Re: [O] Bug: org-dblock-update regression in case of :maxlevel 0 [9.0.5 (9.0.5-elpaplus @ c:/Users/clange/.emacs.d/elpa/org-plus-contrib-20170210/)] |
Date: |
Mon, 13 Feb 2017 21:34:51 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
Hello,
Christoph LANGE <address@hidden> writes:
> I have a clocktable that looks as follows. (Once more, I'll be happy to
> work this out as a minimum working example – later, don't have time
> right now.)
>
> #+BEGIN: clocktable :block 2017-W01 :maxlevel 0 :scope ("filename.org")
> :indent
>
> The output I got for this from an older Org version (9.0.something,
> definitely < 9.0.4) was:
>
> | File | Headline | Time |
> |--------------+------------------+--------|
> | | ALL *Total time* | *1:00* |
> |--------------+------------------+--------|
> | filename.org | *File time* | *1:00* |
>
> :maxlevel 1 would include level-1 headings _in_ this file, like this:
>
> | File | Headline | Time |
> |--------------+------------------+--------|
> | | ALL *Total time* | *1:00* |
> |--------------+------------------+--------|
> | filename.org | *File time* | *1:00* |
> | | Task 1 | 0:05 |
> | | Task 2 | 0:55 |
>
> where filename.org looks like
>
> * Task 1
> * Task 2
> ...
>
>> It sounds like a user error to me.
>
> Maybe the truth is that the handling of :maxlevel 0 was an undocumented
> feature?
I see. It makes sense. I just couldn't find it. Thanks for the
explanation. This is now fixed.
Regards,
--
Nicolas Goaziou