emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Olaf Dietsche <olaf+list.orgmode@olafdietsche.de>
Cc: emacs-orgmode@gnu.org, Tommy Kelly <tommy.kelly@verilab.com>
Subject: Re: Journal versus clock tables: Opposing requirements?
Date: Tue, 8 Nov 2011 10:54:43 +0100	[thread overview]
Message-ID: <0B5C7332-F2CF-483E-B47F-ADA0EB8A03CC@gmail.com> (raw)
In-Reply-To: <87bosngf3t.fsf@rat.lan>


On Nov 8, 2011, at 10:04 AM, Olaf Dietsche wrote:

> Tommy Kelly <tommy.kelly@verilab.com> writes:
> 
>>> OK, that might be what I need then. I thought clock tables grouped
>>> things by headings, not by tags. I'll have a look at the manual.
>> 
>> I'm trying the tagging thing within clock tables, but I can't get it
>> working at all. I've attached a tag to a single headline, and checked
>> that I've got that right by using "C-c a m". Then I added a :tags item
>> to my clock table block but it seems to have no effect. Is this valid:
>> 
>> #+BEGIN: clocktable :maxlevel 2 :scope file :block thisweek :step week
>> :indent :tags test_tag
>> #+END:
>> 
>> I've also tried :tags 'test_tag', :tags '+test_tag' and a bunch of
>> other things, but nothing seems to do anything. What I was expecting
>> was that my clock table, currently filled with lots of items, would be
>> reduced to looking only at the single headline that I've tagged. But
>> it's not -- it just stays as it was before.
> 
> I haven't tried this myself, just looking at the manual. But playing
> around, it seems you need double quotes around your tags match.

Yes.  The clock table parameters are read as lisp syntax, and the
match is a string.

HTH

- Carsten

> 
> Here's a simple example for a start:
> 
> Tagged clock tables  -*- mode: org; fill-column: 78 -*-
> 
> * Shopping							    :errands:
>  :CLOCK:
>  CLOCK: [2011-11-07 Mo 09:45]--[2011-11-07 Mo 09:50] =>  0:05
>  :END:
> * Cleaning							      :house:
>  :CLOCK:
>  CLOCK: [2011-11-07 Mo 08:50]--[2011-11-07 Mo 09:05] =>  0:15
>  :END:
> * Kids								   :children:
>  :CLOCK:
>  CLOCK: [2011-11-07 Mo 08:30]--[2011-11-07 Mo 08:50] =>  0:20
>  :END:
> * Homework							   :children:
>  :CLOCK:
>  CLOCK: [2011-11-07 Mo 13:40]--[2011-11-07 Mo 14:05] =>  0:25
>  :END:
> * Exercises							     :health:
>  :CLOCK:
>  CLOCK: [2011-11-07 Mo 07:30]--[2011-11-07 Mo 07:50] =>  0:20
>  :END:
> 
> #+BEGIN: clocktable :maxlevel 2 :scope file :tags "health"
> Clock summary at [2011-11-08 Di 09:57]
> 
> | Headline     | Time   |
> |--------------+--------|
> | *Total time* | *0:20* |
> |--------------+--------|
> | Exercises    | 0:20   |
> #+END: clocktable
> 
> #+BEGIN: clocktable :maxlevel 2 :scope file :tags "children"
> Clock summary at [2011-11-08 Di 09:58]
> 
> | Headline     |   Time |
> |--------------+--------|
> | *Total time* | *0:45* |
> |--------------+--------|
> | Kids         |   0:20 |
> | Homework     |   0:25 |
> #+END: clocktable
> 
> Regards, Olaf

- Carsten

  reply	other threads:[~2011-11-08  9:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-07  8:31 Journal versus clock tables: Opposing requirements? Tommy Kelly
2011-11-07 11:27 ` Bernt Hansen
2011-11-07 14:55   ` Tommy Kelly
2011-11-08  3:21     ` Bernt Hansen
2011-11-08  8:06       ` Tommy Kelly
2011-11-08  8:23         ` Carsten Dominik
2011-11-08 12:28         ` Bernt Hansen
2011-11-08 17:07         ` Bernt Hansen
2011-11-07 11:38 ` Olaf Dietsche
2011-11-07 14:51   ` Tommy Kelly
2011-11-07 17:19     ` Tommy Kelly
2011-11-08  9:04       ` Olaf Dietsche
2011-11-08  9:54         ` Carsten Dominik [this message]
2011-11-08  9:55         ` Tommy Kelly
2011-11-08 10:00           ` Carsten Dominik
2011-11-08 10:05             ` Sebastien Vauban
2011-11-08 10:15               ` Carsten Dominik
2011-11-08 10:33                 ` Sebastien Vauban
2011-11-08 10:41                 ` Tommy Kelly
2011-11-24 14:57         ` Eric S Fraga
2011-11-24 22:01           ` Olaf Dietsche

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=0B5C7332-F2CF-483E-B47F-ADA0EB8A03CC@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=olaf+list.orgmode@olafdietsche.de \
    --cc=tommy.kelly@verilab.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).