From: Giovanni Ridolfi <giovanni.ridolfi@yahoo.it>
To: B Grobauer <bgrobauer@googlemail.com>
Cc: Emacs-orgmode@gnu.org, Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: [PATCH] New clocktable-feature: Structure clocktable by tags rather than by hierarchy
Date: Mon, 21 Jun 2010 11:10:11 +0200 [thread overview]
Message-ID: <83aaqoda4s.fsf@yahoo.it> (raw)
In-Reply-To: <AANLkTink1gfpc3undRq3t4R6x98zYJDEKYhrlsgO5Lmk@mail.gmail.com> (B. Grobauer's message of "Sun, 20 Jun 2010 13:26:55 +0200")
B Grobauer <bgrobauer@googlemail.com> writes:
>> Does your mechanism see inherited tags?
>
> Yes -- in the sample file, for example, tag inheritance
> is used to mark all sub-nodes of the two top-level trees
> for "Project A" and "Project B" as pertaining to
> those projects, respectively.
Feature request: Is it possible to check also for properies
and not only for tag?
we can add a special PROPERTY: CLOCKTAG
Rationale:
In my setup I have a remember template where I write the task I'm doing.
with some information e.g.:
** reading bibliography
CLOCK: [2010-06-21 lun 09:24]
:PROPERTIES:
:ID: lab
:Type:expected
:People: Giovanni
:Location: computer
:Connection: nil
:CLOCKTAG:PV Project
:Comment:
:END:
If the function checks also the :PROPERTIES: drawer and the existence of
the special PROPERTY: CLOCKTAG I can keep my setup and exploit this
marvellous new feature.
If it's too complicated I will use the tags ;-)
TIA
Giovanni
next prev parent reply other threads:[~2010-06-21 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-20 10:24 [PATCH] New clocktable-feature: Structure clocktable by tags rather than by hierarchy B Grobauer
2010-06-20 10:52 ` Carsten Dominik
2010-06-20 11:26 ` B Grobauer
2010-06-21 9:10 ` Giovanni Ridolfi [this message]
2013-08-26 5:18 ` [PATCH] New clocktable-feature: Structure clocktable bytags " Jeff Kowalczyk
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=83aaqoda4s.fsf@yahoo.it \
--to=giovanni.ridolfi@yahoo.it \
--cc=Emacs-orgmode@gnu.org \
--cc=bgrobauer@googlemail.com \
--cc=carsten.dominik@gmail.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.