emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] Bug: No property change from ‘org-clock-s um’


From: Bernt Hansen
Subject: Re: [O] Bug: No property change from ‘org-clock-s um’
Date: Fri, 06 May 2011 09:56:40 -0400
User-agent: Gnus/5.110017 (No Gnus v0.17) Emacs/23.2 (gnu/linux)

Ben Finney <address@hidden> writes:

> Bernt Hansen <address@hidden> writes:
>
>> I don't think the org-clock-sum function does what you think/want it
>> to do. The docstring says it sets text properties on the headline - so
>> I don't think it is intended to update a CLOCKSUM property in the
>> headings.
>
> I don't underastand the distinction. Isn't the CLOCKSUM property a text
> property? What do I need to know here?

Sorry I didn't explain that very well.  Hopefully this will shed a
little more light on this.

Text properties is an emacs feature where you can add extra (invisible,
and temporary) data to text in an emacs buffer.

An Org-mode properties are part of the org file and normally lives in
the :PROPERTY: drawer.

The column view overlay is displayed using emacs text properties - and
this doesn't alter the data in the org file.  Thus the org-invoice.el
code that queries the _org_ property CLOCKSUM never gets a value.

>
>> These text properties are temporary (ie. not saved in the org file) and
>> I think these are used by the column view overlays for display-only.
>>
>> The org-invoice.el contributed file created by Peter Jones uses a
>> CLOCKSUM property but I'm not sure if this is intended to be updated
>> manually or automatically from the clocking lines in org.  I've CC-ed
>> Peter in case he can shed any light on this.
>
> Thanks. It does seem that they're much the same purpose, so I hope they
> can be unified.

I think the fix is probably to make org-invoice.el look for the CLOCKSUM
text property instead of a CLOCKSUM org-mode property value.
org-invoice.el should probably also automatically call org-clock-sum so
this doesn't need to be a manual step.

Regards,
Bernt




reply via email to

[Prev in Thread] Current Thread [Next in Thread]