From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Lundin Subject: Re: clocktable and :tags Date: Sat, 05 Jun 2010 12:37:06 -0400 Message-ID: <87631x4erx.fsf@fastmail.fm> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from [140.186.70.92] (port=50540 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OKwMu-0001da-5c for emacs-orgmode@gnu.org; Sat, 05 Jun 2010 12:37:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OKwMs-00038j-Iv for emacs-orgmode@gnu.org; Sat, 05 Jun 2010 12:37:08 -0400 Received: from out5.smtp.messagingengine.com ([66.111.4.29]:39911) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OKwMs-00038e-HF for emacs-orgmode@gnu.org; Sat, 05 Jun 2010 12:37:06 -0400 In-Reply-To: (Kristofer Bergstrom's message of "Sat, 5 Jun 2010 09:16:03 -0700") 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: Kristofer Bergstrom Cc: emacs-orgmode@gnu.org Kristofer Bergstrom writes: > Unfortunately, the :tags element of clocktable dynamic blocks does not > seem to be functioning properly. Identical commands on Sebastian's > system worked fine. The problem can be seen below in a test I'm > using. Running C-c C-c while on the clocktable line updates the > timestamp in the clocktable, but the tags element is not being > evaluated. Using your example, it works fine here with the latest org-mode: --8<---------------cut here---------------start------------->8--- #+BEGIN: clocktable :tags "PHONE" :maxlevel 2 :scope file Clock summary at [2010-06-05 Sat 12:29] | L | Headline | Time | |---+----------------------------+--------| | | *Total time* | *0:03* | |---+----------------------------+--------| | 1 | Non work-related project 3 | 0:03 | #+END: --8<---------------cut here---------------end--------------->8--- > Or maybe I should upgrade to a newer version of org-mode? I don't > know how to determine the current version I am using... Type M-x org-version. Or in an org-mode buffer you can use the menu: - Org --> Documentation --> Show version Since the clock report is working fine here with an up-to-date org-mode, I'd recommend trying the most recent release: http://orgmode.org/org-6.36c.tar.gz Best, Matt