emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jeremie Juste <jeremiejuste@gmail.com>
To: 10cadr <cristianrauber@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: LaTeX fragments not being generated due to extra * in tikz env
Date: Wed, 09 Dec 2020 19:16:19 +0100	[thread overview]
Message-ID: <87im9akfpo.fsf@gmail.com> (raw)
In-Reply-To: <CAO-1nSm+xOB2vq3VWUi9D7eeSDt7U3htmnuT=AeUrpUG0CymeQ@mail.gmail.com> (cristianrauber@gmail.com's message of "Tue, 8 Dec 2020 20:57:34 +0000")


Thanks for reporting. Indeed this is an issue that hasn't been fixed
yet. This is the case for most latex environments  

My solution is here

but consider also the idea behind the star

I will try to submit a patch soon.

Best regards,

On Tuesday,  8 Dec 2020 at 20:57, 10cadr wrote:
> I was trying out the new option tex:dvipng. The HTML result was a image
> with the tikz code.
> Turns out, debugging and telling the fragment processor not to delete the
> files, what org generates for the tikz fragment is:
> \begin{tikzpicture*}
> Removing the astherisk would make it work without any workarounds.
> How I got around this was
> #+LATEX_HEADER: \usepackage{environ,amsmath,multicol}
> \NewEnviron{tikzpicture*}[1][]{\begin{tikzpicture}[#1]\BODY\end{tikzpicture}}
> Possibly fixing this issue, will make cross formats much easier.

Jeremie Juste

  reply	other threads:[~2020-12-09 19:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-08 20:57 LaTeX fragments not being generated due to extra * in tikz env 10cadr
2020-12-09 18:16 ` Jeremie Juste [this message]
2020-12-18  0:30   ` Thibault Marin
2020-12-19 12:55     ` Jeremie Juste

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=87im9akfpo.fsf@gmail.com \
    --to=jeremiejuste@gmail.com \
    --cc=cristianrauber@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).