Re: Differentiating org element properties from built-ins?

[Ihor Radchenko <yantar92@posteo.net>]

<tomas@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.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>