From: Carsten Dominik <carsten.dominik@gmail.com>
To: Tommy Kelly <tommy.kelly@verilab.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Journal versus clock tables: Opposing requirements?
Date: Tue, 8 Nov 2011 11:00:49 +0100 [thread overview]
Message-ID: <B41CCCF9-8821-4A0C-8483-2FF71652B4FF@gmail.com> (raw)
In-Reply-To: <CAMg28OsvMtSYH8n2Yqikxwvf+P5N=o2BjqyMotp0p4AJk+aKkA@mail.gmail.com>
On Nov 8, 2011, at 10:55 AM, Tommy Kelly wrote:
>> I haven't tried this myself, just looking at the manual. But playing
>> around, it seems you need double quotes around your tags match.
>
> Ah OK, that works. But it turns out there was a second problem and it
> may be a bug. It looks like any of the clocktable options after
> :indent get ignored. So this works:
>
> #+BEGIN: clocktable :maxlevel 2 :scope file :block thisweek :step week
> :tags "test_tag" :indent
> #+END:
>
> But this doesn't (i.e. the :tags option is ignored)
>
> #+BEGIN: clocktable :maxlevel 2 :scope file :block thisweek :step week
> :indent :tags "test_tag"
You need
:indent t
This is a property list, each key needs a value.
- Carsten
next prev parent reply other threads:[~2011-11-08 10:00 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
2011-11-08 9:55 ` Tommy Kelly
2011-11-08 10:00 ` Carsten Dominik [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B41CCCF9-8821-4A0C-8483-2FF71652B4FF@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--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 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.