Hi Moritz,
Moritz Ulrich ulrich.mor...@googlemail.com writes:
I'm currently running a report on my tasks last month. It works pretty
fine using the following clocktable invocation:
#+BEGIN: clocktable :maxlevel 2 :scope subtree :compact t :timestamp t
#+END:
This gives me a nice exportable clocktable for the current subtree
(which is what I've done for work last month).
However, one thing isn't very nice. One (big) task was clocked over
two consecutive days:
CLOCK: [2012-03-30 Fri 12:45]--[2012-03-30 Fri 18:25] = 5:40
CLOCK: [2012-03-29 Thu 14:45]--[2012-03-29 Thu 19:11] = 4:26
org-clocktable's :timestamp doesn't handle this, showing the task
only with one timestamp in the table. This is as expected as the doc
says: Look for SCHEDULED, DEADLINE, TIMESTAMP and TIMESTAMP_IA, in
this order..
I think org-clocktable should search for CLOCKED too.
If you want two separate lines for the same entry, one for the time
spent on the timestamp'ed day, another one for the time spent the next
day, I think it would be confusing -- the (somewhat implicit) rule in
the clocktable is to have one task per clocked item. Also, this would
require internally processing CLOCK: lines that span over two days,
and this is not trivial.
But perhaps I'm misunderstanding.
Can you provide an example?
--
Bastien
