From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bastien <bzg@gnu.org>
Subject: Re: org-clocktable: Show timestamps for CLOCKED
Date: Sun, 29 Apr 2012 10:47:40 +0200
Message-ID: <87pqaqhnze.fsf@altern.org>
References: <CALw-MDr3b+9vHXJS-RiOamWueN2Vw1vc3wnNGDrSeanE1e5Frw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([208.118.235.92]:42600)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bastienguerry@googlemail.com>) id 1SOQeZ-0001Y7-Lt
	for emacs-orgmode@gnu.org; Sun, 29 Apr 2012 05:42:52 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bastienguerry@googlemail.com>) id 1SOQeX-0005cH-DA
	for emacs-orgmode@gnu.org; Sun, 29 Apr 2012 05:42:51 -0400
Received: from mail-wi0-f177.google.com ([209.85.212.177]:47945)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bastienguerry@googlemail.com>) id 1SOQeX-0005be-48
	for emacs-orgmode@gnu.org; Sun, 29 Apr 2012 05:42:49 -0400
Received: by wibhj13 with SMTP id hj13so1517368wib.12
	for <emacs-orgmode@gnu.org>; Sun, 29 Apr 2012 02:42:47 -0700 (PDT)
In-Reply-To: <CALw-MDr3b+9vHXJS-RiOamWueN2Vw1vc3wnNGDrSeanE1e5Frw@mail.gmail.com>
	(Moritz Ulrich's message of "Fri, 20 Apr 2012 13:23:03 +0200")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Moritz Ulrich <ulrich.moritz@googlemail.com>
Cc: emacs-orgmode@gnu.org

Hi Moritz,

Moritz Ulrich <ulrich.moritz@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