Hi,
I looked into generated html, not result of org-element-property.
But you're right: org-element-property works exactly as you say.
I'll change the patch to ob-core.el to reflect behavior of
org-element-property.
With best regards,
Vasil
> Of course not. With:
>
> #+attr_html: alt="big image" width="100%"
> file:123.png
>
> (org-element-property :attr_html (org-element-at-point)) with point at
> "file:..." will return ("alt=\"big image\" width=\"100%\"") while on the
> following example:
>
> #+attr_html: alt="big image" width="100%"
>
> file:123.png
>
> it will return nil.
>
>> That is why I think that it is not necessary to make org-babel behavior
>> different from org-elements (to dissalow empty lines between #+attr and
>> #+results when it searches results block), at least for now.
>
> Babel behaviour is already slightly different from Elements's. In the
> long run it will be necessary to correct this.
>
>> PS: Is there any good documentation and explanation of org-mode
>> internals? I could help a little with rewritting org-babel to use
>> org-elements.
>
> You may have a look at the comments at the start of org-elements.el. At
> some point, I will have to write an Info doc about this library, unless
> I postpone it until the end of time.
>
>
> Regards,
