etc/ORG-NEWS: Clarify that `org-element-property' can be used with deferred

* etc/ORG-NEWS (Internal structure of Org parse tree has been
changed): Clarify when one needs to adjust for the breaking change
introducing deferred properties.
This commit is contained in:
Ihor Radchenko 2023-08-09 10:26:35 +03:00
parent f159adc269
commit 8ed3887821
No known key found for this signature in database
GPG Key ID: 6470762A7DA11D8B
1 changed files with 6 additions and 3 deletions

View File

@ -70,9 +70,12 @@ Instead, they are kept in a special vector value of a new
If there is a need to traverse all the node properties, a new API
function ~org-element-properties-map~ can be used.
Properties and their values can now be deferred to avoid overheads when
parsing. They are calculated lazily, when the value/property is
requested by getters.
Properties and their values can now be deferred to avoid overheads
when parsing. They are calculated lazily, when the value/property is
requested by ~org-element-property~ and other getter functions. Using
~plist-get~ to retrieve values of =PROPERTIES-PLIST= is not
recommended as deferred properties will not be resolved in such
scenario.
New special property =:secondary= is used internally to record which
properties store secondary objects.