From: Bernt Hansen <bernt@norang.ca>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Ben Finney <ben+emacs@benfinney.id.au>, emacs-orgmode@gnu.org
Subject: Re: Bug: No property change from ‘org-clock-sum’
Date: Fri, 06 May 2011 11:55:03 -0400 [thread overview]
Message-ID: <87k4e3j02w.fsf@norang.ca> (raw)
In-Reply-To: <A4E0ADB0-412B-4E5B-951D-A442F6504EBB@gmail.com> (Carsten Dominik's message of "Fri, 6 May 2011 17:30:30 +0200")
Carsten Dominik <carsten.dominik@gmail.com> writes:
> No. CLOCKSUM is a special property, and it can be used to
> access the clocking sum of an entry after (org-clock-sum) has
> been called. This is what org-invoice does. It calls
> org-clock-sum to do the computation, and then used the property
> API to get to the value.
>
> However, I seen now that there is a bug here, cause by a
> rewrite (for speed) of property access some time ago.
> After that rewrite, the special CLOCKSUM property used
> by org-invoice.el was no longer accessible.
>
> This problem has just been fixed, so with the current git master,
> org-invoice.el should work again.
Ah! Thanks Carsten. It does indeed return values after this fix.
However there are numerous problems with the resulting invoice for a
sample tree I have with clocked data.
I'll send these details to the list shortly.
Regards,
Bernt
next prev parent reply other threads:[~2011-05-06 15:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 21:51 Bug: No property change from ‘org-clock-sum’ Ben Finney
2011-05-06 0:14 ` Ben Finney
2011-05-06 1:43 ` Bernt Hansen
2011-05-06 6:34 ` Ben Finney
2011-05-06 13:56 ` Bernt Hansen
2011-05-06 15:30 ` Carsten Dominik
2011-05-06 15:55 ` Bernt Hansen [this message]
2011-05-07 0:48 ` Ben Finney
2011-05-06 14:43 ` Peter Jones
2011-05-06 16:32 ` Bernt Hansen
2011-05-06 15:31 ` Carsten Dominik
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=87k4e3j02w.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=ben+emacs@benfinney.id.au \
--cc=carsten.dominik@gmail.com \
--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).