* org-clocktable: Show timestamps for CLOCKED
@ 2012-04-20 11:23 Moritz Ulrich
2012-04-29 8:47 ` Bastien
0 siblings, 1 reply; 2+ messages in thread
From: Moritz Ulrich @ 2012-04-20 11:23 UTC (permalink / raw)
To: emacs-orgmode
Hello,
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.
--
Moritz Ulrich
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: org-clocktable: Show timestamps for CLOCKED
2012-04-20 11:23 org-clocktable: Show timestamps for CLOCKED Moritz Ulrich
@ 2012-04-29 8:47 ` Bastien
0 siblings, 0 replies; 2+ messages in thread
From: Bastien @ 2012-04-29 8:47 UTC (permalink / raw)
To: Moritz Ulrich; +Cc: emacs-orgmode
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-04-29 9:42 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-04-20 11:23 org-clocktable: Show timestamps for CLOCKED Moritz Ulrich
2012-04-29 8:47 ` Bastien
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).