On Sun, Sep 22, 2024 at 05:15:25PM +0000, Ihor Radchenko wrote: > <to...@tuxteam.de> writes: > > > I do see foo and bar (well, OK, :FOO and :BAR) with their values, but lots > > of other (let's call them "built-ins") like :begin and :post-affiliated. > > > > How do I keep those apart? Or do I have to resort to running regexps through > > the buffer? > > (defun org-element-headline-parser (&optional _ raw-secondary-p) > "Parse a headline. > > Return a new syntax node of `headline' type containing `:raw-value', > `:title', `:begin', `:end', `:pre-blank', `:contents-begin' and > `:contents-end', `:level', `:priority', `:tags', `:todo-keyword', > `:todo-type', `:scheduled', `:deadline', `:closed', `:archivedp', > `:commentedp' `:footnote-section-p', `:post-blank' and > `:post-affiliated' properties. > > The plist also contains any property set in the property drawer, > with its name in upper cases and colons added at the > beginning (e.g., `:CUSTOM_ID'). > > So, properties from the property drawer are always upcased.
Thanks for that, Ihor I ended up regexping my was through (which brought about some other advantages with it; I'm using those props to communicate with other things outside, and there, keeping the keys's cases is a nice-to-have). Actually, the case treatment of property names is one of the most acute pain points in Org for me, but this ship has sailed :-) Cheers & thanks again for your help. -- tomás
signature.asc
Description: PGP signature
