From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Jeremy Reeve <jeremy.reeve81@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Export results of code literal blocks (Jekyll directory structure) xpost emacs.stackexchange
Date: Wed, 28 Jun 2017 15:22:41 +0200 [thread overview]
Message-ID: <87zicsfdr2.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAGdd8vGR7yTUji69G7vG4xxguTwGgYXVBe7P1Mxn0RO9s5SXEQ@mail.gmail.com> (Jeremy Reeve's message of "Sun, 25 Jun 2017 11:33:39 +1200")
Hello,
Jeremy Reeve <jeremy.reeve81@gmail.com> 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
next prev parent reply other threads:[~2017-06-28 13:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-24 23:33 Export results of code literal blocks (Jekyll directory structure) xpost emacs.stackexchange Jeremy Reeve
2017-06-28 13:22 ` Nicolas Goaziou [this message]
2017-06-30 1:17 ` Jeremy Reeve
2017-06-30 7:08 ` Nicolas Goaziou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zicsfdr2.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=jeremy.reeve81@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).