From: Jeremie Juste <jeremiejuste@gmail.com>
To: Thibault Marin <thibault.marin@gmx.com>
Cc: emacs-orgmode@gnu.org, 10cadr <cristianrauber@gmail.com>
Subject: Re: LaTeX fragments not being generated due to extra * in tikz env
Date: Sat, 19 Dec 2020 13:55:44 +0100 [thread overview]
Message-ID: <87wnxe7y5r.fsf@gmail.com> (raw)
In-Reply-To: <87h7ok3qi2.fsf@dell-desktop.WORKGROUP> (Thibault Marin's message of "Thu, 17 Dec 2020 19:30:13 -0500")
Hello Thibault,
Many thanks. This looks like a reasonable trade off for me.
Best regards,
Jeremie
On Thursday, 17 Dec 2020 at 19:30, Thibault Marin wrote:
> Hi,
>
> I introduced the change that broke the behavior. The attached patch
> seems to fix the issue for me, does it look reasonable?
>
> Thanks,
>
> thibault
>
> On 2020-12-09T13:16:19-0500, Jeremie Juste wrote:
>
> Hello,
>
> 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
> https://www.mail-archive.com/emacs-orgmode@gnu.org/msg129974.html
>
> but consider also the idea behind the star
> https://www.mail-archive.com/emacs-orgmode@gnu.org/msg129976.html
>
> I will try to submit a patch soon.
>
> Best regards,
> Jeremie
>
> 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}
> > #+LATEX_HEADER:
> > \NewEnviron{tikzpicture*}[1][]{\begin{tikzpicture}[#1]\BODY\end{tikzpicture}}
> >
> > Possibly fixing this issue, will make cross formats much easier.
>
> --
> Jeremie Juste
>
>
>
--
Jeremie Juste
prev parent reply other threads:[~2020-12-19 12:56 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
2020-12-18 0:30 ` Thibault Marin
2020-12-19 12:55 ` Jeremie Juste [this message]
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=87wnxe7y5r.fsf@gmail.com \
--to=jeremiejuste@gmail.com \
--cc=cristianrauber@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=thibault.marin@gmx.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).