emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matthew Lundin <mdl@imapmail.org>
To: Francesco Pizzolante <fpz@missioncriticalit.com>
Cc: mailing-list-org-mode <emacs-orgmode@gnu.org>
Subject: Re: Record extra info for each time block
Date: Mon, 06 Apr 2009 14:50:34 -0500	[thread overview]
Message-ID: <m2k55xmuid.fsf@fastmail.fm> (raw)
In-Reply-To: <uy6udq1cr.fsf@missioncriticalit.com> (Francesco Pizzolante's message of "Mon\, 06 Apr 2009 16\:54\:28 +0200")

Hi Francesco

"Francesco Pizzolante" <fpz@missioncriticalit.com> writes:

> But sometimes, you also need to record some other information related
> to that time block, for example, the distance you had to drive to go
> to the meeting or some costs (like parking costs) that you had to pay
> for it.
>
> Example:
>
> * Project1
>   ** Meetings
>      :LOGBOOK:
>      CLOCK: [2009-03-02 mon. 10:00]--[2009-03-02 mon. 12:30] =>  2:30
>             ----> 15 kilometers
>      CLOCK: [2009-03-03 tue. 09:30]--[2009-03-03 tue. 12:30] =>  3:00
>             ----> 15 kilometers + 12,00 EUR
>      :END:
>
> Is there a way to record this information? If not, what is your
> advice?
>

You could also record this information as properties. E.g.,

,----
| * Meetings
|   :PROPERTIES:
|   :COLUMNS:  %30ITEM %CLOCKSUM %10distance{+} %10expenses{$}
|   :END:
| ** Meeting One
|    :LOGBOOK:
|    CLOCK: [2009-04-06 Mon 13:25]--[2009-04-06 Mon 14:37] =>  1:12
|    :END:
|    :PROPERTIES:
|    :distance: 15
|    :expenses: 13.45
|    :END:
| 
| ** Meeting Two
|    :LOGBOOK:
|    CLOCK: [2009-04-06 Mon 16:41]--[2009-04-06 Mon 18:41] =>  2:00
|    :END:
|    :PROPERTIES:
|    :distance: 28
|    :expenses: 22.31
|    :END:
| 
`----

> Of course, it would be nice to get a final table with everything
> summed up: total work, total kilometers, total fees.

If you add a column line (as in the example above) you can use column
view (C-c C-x C-c) to get a nice overview with everything summed up in the top
heading. Or you could capture the data in a table (C-x C-c i). E.g.,

,----
| ** Summary 
| #+BEGIN: columnview :hlines 1 :id local
| | ITEM           | CLOCKSUM | distance | expenses |
| |----------------+----------+----------+----------|
| | * Meetings     |     3:12 |       43 |    35.76 |
| | ** Meeting One |     1:12 |       15 |    13.45 |
| | ** Meeting Two |     2:00 |       28 |    22.31 |
| #+END:
`----

The manual has a lot of great info on setting properties.

- Matt

  parent reply	other threads:[~2009-04-06 19:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06 14:54 Record extra info for each time block Francesco Pizzolante
2009-04-06 15:52 ` John Rakestraw
2009-04-06 19:50 ` Matthew Lundin [this message]
     [not found]   ` <m2k55xmuid.fsf-97jfqw80gc6171pxa8y+qA@public.gmane.org>
2009-04-07  9:54     ` Francesco Pizzolante

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=m2k55xmuid.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=fpz@missioncriticalit.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).