From: "Éric Würbel" <eric.wurbel@univ-amu.fr>
To: Orgmode list <emacs-orgmode@gnu.org>
Subject: Latex code blocks HTML export still broken
Date: Thu, 01 Dec 2016 10:47:46 +0100 [thread overview]
Message-ID: <87twaof0al.fsf@univ-amu.fr> (raw)
When exporting a latex code block as a png image in an HTML page, Org
complains that the pdf file was not produced.
Minimal org document example :
#+BEGIN_SRC org
#+TITLE LaTeX export minimal test
* Let's go
A really interresting algorithm :
#+header: :headers '( "\\renewcommand{\\familydefault}{\\sfdefault}" "\\usepackage{lmodern}" "\\usepackage{algpseudocode}" )
#+header: :file algo.png
#+header: :imagemagick yes :fit yes
#+header: :results raw :iminoptions -density 600 :imoutoptions -geometry 1200
#+BEGIN_SRC latex
\begin{algorithmic}[1]
\Function{triSauvegarde}{nom\_fichier : String}
\State tab $\gets$ \Call{copie}{leContenu}
\State \Call{trier}{tab}
\State \Call{sauvegarder}{nom\_fichier}
\EndFunction
\end{algorithmic}
#+END_SRC
#+END_SRC
When trying to export to html with C-c C-e h h, org complains :
org-compile-file: File "/tmp/babel-2370po9/latex-237073Q.pdf" wasn't produced. See "*Org PDF LaTeX Output*" for details
In fact the file is produced, but directly in
/tmp/latex-237073Q.pdf. (no babel-2370po9 subdir).
So, compared to the previous version of the bug, we have progressed :
temporary pdf are not produced in the current directory anymore, but org
does not know yet where to find them ;o)
Regards
E.
--
Éric Würbel
http://eric.wurbel.perso.luminy.univ-amu.fr/
Enseignement: IUT R&T, directeur des études 1A
Recherche: LSIS, UMR7296 http://www.lsis.org/
next reply other threads:[~2016-12-01 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 9:47 Éric Würbel [this message]
2016-12-01 15:53 ` Latex code blocks HTML export still broken Nick Dokos
2016-12-02 12:34 ` Éric Würbel
2016-12-01 17:40 ` Nick Dokos
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=87twaof0al.fsf@univ-amu.fr \
--to=eric.wurbel@univ-amu.fr \
--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).