From: Emmanuel Charpentier <emm.charpentier@free.fr>
To: Timothy <tecosaur@gmail.com>, John Kitchin <jkitchin@andrew.cmu.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: LaTeX-producing code : how to export results to HTML/ODT ?
Date: Wed, 14 Jul 2021 10:16:16 +0200 [thread overview]
Message-ID: <82404a56d74ebd20718d31c6cd914dbd57dae11b.camel@free.fr> (raw)
In-Reply-To: <87czrljt1k.fsf@gmail.com>
"Raw" LaTeX code export to ODT always worked if =tex= (and possibly
=org-latex-to-mathml-convert-command=) were correctly set.
The problem is that "raw" output is no longer recognized as the
function result. If the function is reran, the result will be output
twice : once by the function execution and once by the "#+results:"
paragraph.
John's black magic with drawers allows to keep the link between
function and results.
HTH,
--
Emmanuel Charpentier
Le mercredi 14 juillet 2021 à 14:41 +0800, Timothy a écrit :
>
> John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
> > #+RESULTS: foo
> > :results:
> > \[\displaystyle{\sin\left(\frac{a}{b}\right)}\]
> > :end:
> >
> > the key is the drawer I think.
>
> FYI as of
> https://code.orgmode.org/bzg/org-mode/commit/b90b850ae8be46a1ebe7d13b05ad79869e8d1032
> a LaTeX environment will "just work". i.e.
>
> #+RESULTS:
> \begin{equation*}
> \displaystyle{\sin\left(\frac{a}{b}\right)}
> \end{equation*}
>
> This is currently made use of in the new ob-julia (WIP).
>
> --
> Timothy
next prev parent reply other threads:[~2021-07-14 8:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-04 7:45 LaTeX-producing code : how to export results to HTML/ODT ? Emmanuel Charpentier
2021-07-04 18:10 ` John Kitchin
2021-07-04 18:51 ` Emmanuel Charpentier
2021-07-04 19:04 ` John Kitchin
2021-07-04 21:13 ` Emmanuel Charpentier
2021-07-14 6:41 ` Timothy
2021-07-14 8:16 ` Emmanuel Charpentier [this message]
2021-07-04 21:11 ` Emmanuel Charpentier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=82404a56d74ebd20718d31c6cd914dbd57dae11b.camel@free.fr \
--to=emm.charpentier@free.fr \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
--cc=tecosaur@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.