Re: [O] Export results of code literal blocks (Jekyll directory structure) xpost emacs.stackexchange

[Nicolas Goaziou]

Hello,

Jeremy Reeve <address@hidden> writes:

> Org-mode newbie here.  Please be gentle.

Do you have any reason to think we will not be gentle?

  "We have a squeaker today, class. Isn't he cute?"

> I'm trying to follow the recipe for exporting Org-mode documents for
> processing by Jekyll. My publishing org-publish-project-alist is
> configured to place exported html in my _posts directory and take
> images and place them in _posts/assets with org-publish-attachment.
> This modification of directory structure seems to be the root of the
> problem.

[...]

> #+RESULTS: [[file:../images/hw1-p3.png]]
>
> #+BEGIN_EXPORT html
> <figure>
>   <img
>   src="{{ site.url }}/assets/hw1-p3.png"
>   alt="Problem 3 visualisation">
>   <figcaption>Problem 3 visualisation</figcaption>
> </figure>
> #+END_EXPORT html
>
> The end result I would like is to have the link to the result of the
> literal code block automatically generated either such that it is not
> exported as an inline image (as the relative path is incorrect) and be
> forced to manually add a correct link for HTML export or have the
> inline image link transformed such that it is correct.

Can't you write a function that fixes generated links? See
`org-export-before-parsing-hook'.

> Also, the above snippet exports everything including the "BEGIN
> export" which I think shouldn't happen but I'll examine that
> separately.

The closing line is wrong. It should be "#+end_export". Use `M-x
org-lint' to find this kind of problem.

Regards,

-- 
Nicolas Goaziou