From: Bernt Hansen <bernt@norang.ca>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Carsten Dominik <carsten@orgmode.org>, emacs-orgmode@gnu.org
Subject: Re: Re: Agenda clock report - adding new columns
Date: Thu, 16 Apr 2009 16:55:42 -0400 [thread overview]
Message-ID: <87zlegwc6p.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <F921D533-97FE-4D9A-A970-04B59DA65350@gmail.com> (Carsten Dominik's message of "Thu\, 16 Apr 2009 22\:31\:44 +0200")
Carsten Dominik <carsten.dominik@gmail.com> writes:
> On Apr 16, 2009, at 8:05 PM, Bernt Hansen wrote:
>
>> David Bremner <bremner@unb.ca> writes:
>>
>>> There is the possibility of :formula parameter for clocktable's,
>>> which
>>> can be added to the agenda clocktable with
>>> org-agenda-clockreport-parameter-plist.
>>
>> Cool - I've never used that yet :). Is there a way to get at property
>> values from a :formula entry? I haven't figured out how to do that
>> yet
>> -- all I want to do is display some user entered property value (or
>> blank if it doesn't exist).
>
> Not easily.
> In principle, the headings in the clock table are links. I could
> actually give them markers. Then, an elisp formula could go back to
> the original buffer and the the property from there.
>
> The question is: is it worth it.
No it's not -- at least not just for this mini-application. I can
accomplish what I want easily enough with just changing the task heading
text a bit. That's fine for what I want.
Thanks for thinking about out :)
-Bernt
prev parent reply other threads:[~2009-04-16 20:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 15:40 Agenda clock report - adding new columns Bernt Hansen
2009-04-16 17:02 ` Bernt Hansen
2009-04-16 17:14 ` David Bremner
2009-04-16 18:05 ` Bernt Hansen
2009-04-16 20:31 ` Carsten Dominik
2009-04-16 20:55 ` Bernt Hansen [this message]
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=87zlegwc6p.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=carsten.dominik@gmail.com \
--cc=carsten@orgmode.org \
--cc=emacs-orgmode@gnu.org \
/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).