From: Paul Rudin <paul-sqPYmOVXOov10XsdtD+oqA@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: clock-in and clock-out columns for clock-table
Date: Sun, 12 Oct 2014 15:35:13 +0100 [thread overview]
Message-ID: <8761fp1hlq.fsf@rudin.co.uk> (raw)
In-Reply-To: 87h9zalq4o.fsf@bzg.ath.cx
Bastien <bzg-mXXj517/zsQ@public.gmane.org> writes:
> Hi Paul,
>
> Paul Rudin <paul-sqPYmOVXOov10XsdtD+oqA@public.gmane.org> 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.
prev parent reply other threads:[~2014-10-12 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 18:44 clock-in and clock-out columns for clock-table Paul Rudin
2014-10-11 12:58 ` Bastien
2014-10-12 14:35 ` Paul Rudin [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8761fp1hlq.fsf@rudin.co.uk \
--to=paul-sqpymovxoov10xsdtd+oqa@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.