Bastien <b...@gnu.org> writes: > Hi Paul, > > Paul Rudin <p...@rudin.co.uk> writes: > >> Is there a way to coerce a clock table to include the clock in and clock >> out information? > > Can you give a literal example of the desired table output? >
The kind of thing I have in mind is we have a file containing: * Task 1 CLOCK: [2014-10-12 Sun 15:20]--[2014-10-12 Sun 15:25] => 0:05 CLOCK: [2014-10-12 Sun 15:15]--[2014-10-12 Sun 15:20] => 0:05 Then at the moment we can get a clock table like: #+BEGIN: clocktable :maxlevel 2 :scope subtree #+CAPTION: Clock summary at [2014-10-12 Sun 15:23] | Headline | Time | |--------------+--------| | *Total time* | *0:10* | |--------------+--------| | Task 1 | 0:10 | #+END: But what I was after was a table something like this: #+BEGIN: clocktable :maxlevel 2 :scope subtree #+CAPTION: Clock summary at [2014-10-12 Sun 15:23] | Headline | Start time | Stop time | Elapsed time | |--------------+----------------------+----------------------+--------------| | *Total time* | | | *0:10* | |--------------+----------------------+----------------------+--------------| | Task 1 | 2014-10-12 Sun 15:15 | 2014-10-12 Sun 15:20 | 0:05 | | Task 1 | 2014-10-12 Sun 15:20 | 2014-10-12 Sun 15:25 | 0:05 | #+END: So, rather than aggregating the time from each separate time range associated with a task into one row, we get a different row for each time range.
