From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Lundin Subject: Re: Record extra info for each time block Date: Mon, 06 Apr 2009 14:50:34 -0500 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LquqJ-0000Ey-44 for emacs-orgmode@gnu.org; Mon, 06 Apr 2009 15:50:51 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LquqE-0000Cy-67 for emacs-orgmode@gnu.org; Mon, 06 Apr 2009 15:50:50 -0400 Received: from [199.232.76.173] (port=44481 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LquqD-0000Cu-Ta for emacs-orgmode@gnu.org; Mon, 06 Apr 2009 15:50:45 -0400 Received: from out2.smtp.messagingengine.com ([66.111.4.26]:47320) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LquqD-0003eg-Jq for emacs-orgmode@gnu.org; Mon, 06 Apr 2009 15:50:45 -0400 In-Reply-To: (Francesco Pizzolante's message of "Mon\, 06 Apr 2009 16\:54\:28 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Francesco Pizzolante Cc: mailing-list-org-mode Hi Francesco "Francesco Pizzolante" 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