From: Bastien <bzg@gnu.org>
To: Moritz Ulrich <ulrich.moritz@googlemail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-clocktable: Show timestamps for CLOCKED
Date: Sun, 29 Apr 2012 10:47:40 +0200 [thread overview]
Message-ID: <87pqaqhnze.fsf@altern.org> (raw)
In-Reply-To: <CALw-MDr3b+9vHXJS-RiOamWueN2Vw1vc3wnNGDrSeanE1e5Frw@mail.gmail.com> (Moritz Ulrich's message of "Fri, 20 Apr 2012 13:23:03 +0200")
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
prev parent reply other threads:[~2012-04-29 9:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 11:23 org-clocktable: Show timestamps for CLOCKED Moritz Ulrich
2012-04-29 8:47 ` Bastien [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pqaqhnze.fsf@altern.org \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=ulrich.moritz@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).