From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Rudin Subject: Re: clock-in and clock-out columns for clock-table Date: Sun, 12 Oct 2014 15:35:13 +0100 Message-ID: <8761fp1hlq.fsf@rudin.co.uk> References: <87d2ad2bk4.fsf@rudin.co.uk> <87h9zalq4o.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain Return-path: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org Bastien writes: > Hi Paul, > > Paul Rudin 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.