From: Jeremy Reeve <jeremy.reeve81@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Export results of code literal blocks (Jekyll directory structure) xpost emacs.stackexchange
Date: Sun, 25 Jun 2017 11:33:39 +1200 [thread overview]
Message-ID: <CAGdd8vGR7yTUji69G7vG4xxguTwGgYXVBe7P1Mxn0RO9s5SXEQ@mail.gmail.com> (raw)
Org-mode newbie here. Please be gentle. Posted on Stack Exchange
before I found the official list.
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.
#+BEGIN_SRC python :results value file
import numpy as np
import matplotlib.pyplot as plt
from mpl_toolkits.mplot3d import Axes3D
p1 = np.array([0,4,4])
p2 = np.array([4,-4,4])
p3 = np.array([2,2,-4])
fig = plt.figure()
ax = fig.gca(projection='3d')
ax.set_aspect("equal")
#draw the arrow
ax.quiver(p1[0],p1[1],p1[2],p2[0],p2[1],p2[2],length=1.0)
ax.quiver(p1[0],p1[1],p1[2],p3[0],p3[1],p3[2],length=1.0)
ax.set_xlim([-5, 5])
ax.set_ylim([-5, 5])
ax.set_zlim([-5, 5])
plt.savefig('../images/hw1-p3.png')
return '../images/hw1-p3.png'
#+END_SRC
#+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.
Suggestions like "Don't use Jekyll" are fine so long as it is
accompanied with an alternative and explanation as to why. I see some
people have written custom Org-mode Jekyll plugins like
https://github.com/eggcaker/jekyll-org and am wondering if these are a
better route.
Also, the above snippet exports everything including the "BEGIN
export" which I think shouldn't happen but I'll examine that
separately.
Regards...Jeremy
Org mode version 9.0.5 (9.0.5-elpa @ /Users/xxx/.emacs.d/elpa/org-20170210/)
GNU Emacs 25.1.1 (x86_64-apple-darwin13.4.0, NS appkit-1265.21 Version
10.9.5 (Build 13F1911)) of 2016-09-18
next reply other threads:[~2017-06-24 23:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-24 23:33 Jeremy Reeve [this message]
2017-06-28 13:22 ` Export results of code literal blocks (Jekyll directory structure) xpost emacs.stackexchange Nicolas Goaziou
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=CAGdd8vGR7yTUji69G7vG4xxguTwGgYXVBe7P1Mxn0RO9s5SXEQ@mail.gmail.com \
--to=jeremy.reeve81@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).