From: Sebastian Hofer <sebhofer@gmail.com>
To: emacs-orgmode@gnu.org
Subject: bug(?) in org-preview-latex-fragment
Date: Sun, 28 Nov 2010 19:38:59 +0100 [thread overview]
Message-ID: <87bp59cmyk.wl%sebhofer@gmail.com> (raw)
Hi all,
it seems that org-preview-latex-fragment does not process \include{} commands in the LATEX_HEADER (while it does process \newcommand). It this supposed to be like that? If not, can it be changed or worked around somehow?
TIA
Sebastian
Minimal example:
test.org:
===================================
#+LATEX_CLASS: article
#+LATEX_HEADER: \include{commands}
#+LATEX_HEADER: \newcommand{\x}{X}
* This works
$\x$
* This doesn't
$\y$
===================================
commands.tex:
===================================
\newcommand{\y}{Y}
===================================
next reply other threads:[~2010-11-28 18:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-28 18:38 Sebastian Hofer [this message]
2011-02-12 19:32 ` bug(?) in org-preview-latex-fragment Bastien
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=87bp59cmyk.wl%sebhofer@gmail.com \
--to=sebhofer@gmail.com \
--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).