emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jeremie Juste <jeremiejuste@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: latex fragments compilation error when exporting to html
Date: Wed, 02 Sep 2020 08:12:01 +0200	[thread overview]
Message-ID: <87a6y8ogge.fsf@gmail.com> (raw)
In-Reply-To: <87tuwhnthi.fsf@gmail.com> (Jeremie Juste's message of "Tue, 01 Sep 2020 22:15:53 +0200")


I have found the culprit in the end. It was the function
org-html--unlabel-latex-environment, int he ox-html.el file.

I'm not sure this function is useful as I think it is better to give the
user control on his environment (labelled or unlabelled) directly in his
org file. I'm I missing something else about the use of this function?

Anyway it was a good experience at debugging elisp.

diff --git a/lisp/ox-html.el b/lisp/ox-html.el
index 55d017529..b2a5d6d36 100644
--- a/lisp/ox-html.el
+++ b/lisp/ox-html.el
@@ -2891,7 +2891,7 @@ CONTENTS is nil.  INFO is a plist holding contextual information."
      ((assq processing-type org-preview-latex-process-alist)
       (let ((formula-link
-              (org-html--unlabel-latex-environment latex-frag)
+              latex-frag
               processing-type info)))
         (when (and formula-link (string-match "file:\\([^]]*\\)" formula-link))
           (let ((source (org-export-file-uri (match-string 1 formula-link))))

Best regards,

- GNU Emacs 28.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.5, cairo version 1.16.0) of 2020-09-01
- Org mode version 9.3.7 (release_9.3.7-725-g7bc18e @ /home/djj/src/org-mode/lisp/)

  reply	other threads:[~2020-09-02  6:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-31 20:24 latex fragments compilation error when exporting to html Jeremie Juste
2020-08-31 21:57 ` Nick Dokos
2020-09-01  5:15   ` Jeremie Juste
2020-09-01  9:06 ` Eric S Fraga
2020-09-01  9:36   ` Jeremie Juste
2020-09-01 10:48     ` Colin Baxter
2020-09-01 10:07   ` Jeremie Juste
2020-09-01 20:15   ` Jeremie Juste
2020-09-02  6:12     ` Jeremie Juste [this message]
2020-09-02  7:40       ` Thibault Marin

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:

  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=87a6y8ogge.fsf@gmail.com \
    --to=jeremiejuste@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).