Re: Bug: [PATCH] Org-babel: separate #+attr_... for code block and for results block [7.9.3d (release_7.9.3d-834-g60083a.dirty @ /home/vdyadov/Work/Tools/emacs/org-mode/lisp/)]

[Nicolas Goaziou <n.goaziou@gmail.com>]

vdyadov@elvees.com (Дядов Васил Стоянов) writes:

> Why syntax is invalid? 

Affiliated keywords have to be put above elements they refer to, without
a blank line in-between.

> I've taken a look at the source code in org-elements.el and found that
> it is taking into account some expressions, like #+results: and so
> on(see org-element-affiliated-keywords, org-element--affiliated-re)
> when attaching properties to objects.
>
> And everything works fine (attributes were attached to right objects),
> except org-babel strategy for searching #+results: expression for
> updating results.
>
> What could you suggest in my case? When I put attributes right before
> link to the image file, I get:
>
> initial code:
>
> ,----
> | #+begin_src ditaa :file 123.png :cache yes
> | ...
> | #+end_src
> |  
> | #+results[f8f8...]:
> | #+attr_html: alt="big image" width="100%"
> | file:123.png
> `----
>
> C-c C-c, result:
>
> ,----
> | #+begin_src ditaa :file 123.png :cache yes
> | ...
> | #+end_src
> |  
> | #+results[f8f8...]:
> | file:123.png
> | 
> | #+attr_html: alt="big image" width="100%"
> | file:123.png
> `----

Elements doesn't care about order for affiliated keywords (here results
and attr_html), but Babel, which isn't built on Elements (yet), does.

Hence, I suggest:

  #+attr_html: ...
  #+results: ...
  file


Regards,

-- 
Nicolas Goaziou