Ihor Radchenko writes:
> Thanks for the clarification. I was not sure if it is intended.
> I was mislead about this 2 times because of docstring, though it is
> clear from the source code.
I fixed the docstring. Thank you.
>> Luckily, headlines are exactly where you do _not_ need Element
> `org-element-at-point' returns only a partial parse tree. It never goes
> higher than the current top-level element, i.e., from an element, you
> cannot go up to the headline just following :parent.
Thanks for the clarification. I was not sure if it is intended.
I was mislead about this 2 times
Hello,
Ihor Radchenko writes:
>> Probably the docstring needs to be adapted - Nicolas knows this area
>> better than me.
>
> Do you mean that :parent property may not always be present?
`org-element-at-point' returns only a partial parse tree. It never goes
higher than the current top-level
Ihor Radchenko writes:
>> Probably the docstring needs to be adapted - Nicolas knows this area
>> better than me.
>
> Do you mean that :parent property may not always be present?
I don't know, I hope Nicolas can handle this.
--
Bastien
> Probably the docstring needs to be adapted - Nicolas knows this area
> better than me.
Do you mean that :parent property may not always be present?
If so, it is quite disappointing. It would be helpful to be able to find
parent of any element at point (especially, in conjunction with
Hi Ihor,
Ihor Radchenko writes:
> According to org-element-at-point docstring, "Properties depend on
> element or object type, but always include :begin, :end, :parent and
> :post-blank properties.".
Probably the docstring needs to be adapted - Nicolas knows this area
better than me.
Best,
