emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Stefan Otte <stefan.otte@gmail.com>
To: Robert Klein <roklein@roklein.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-preview-latex-fragment ignores \includes in the LATEX_HEADER
Date: Thu, 28 May 2015 11:21:13 +0200	[thread overview]
Message-ID: <CAFync2gQQ9+cyfVSbMneGiu0ZJkBpJRbV=hq0hFUQZ=Gxhhezw@mail.gmail.com> (raw)
In-Reply-To: <20150527153722.5ed5e2db@pckr150.mpip-mainz.mpg.de>

Hey,

"\input" does not solve the problem. Still no preview images. (The pdf
export still works as expected.)


Best,
 Stefan



On Wed, May 27, 2015 at 3:37 PM, Robert Klein <roklein@roklein.de> wrote:
> Hi,
>
> On Wed, 27 May 2015 15:02:02 +0200
> Stefan Otte <stefan.otte@gmail.com> wrote:
>
>> Hey,
>>
>> I'm using orgmode with lots of LaTeX for equations. A typical document
>> start with
>>
>>   #+TITLE: Some Title
>>   #+LaTeX_HEADER: \include{commands}
>>
>> commands.tex contains commands like:
>>   \newcommand{\RRR}{{\mathbb{R}}}
>>
>> The pdf export works flawlessly, however `org-preview-latex-fragment`
>> seems to ignore "\include{commands}", i.e., equations that use
>> commands that are defined in commands.tex are rendered as blank/empty
>> image.
>>
>> Is it the intended behavior that `org-preview-latex-fragment` ignores
>> "\include", is it a bug, or is there a better way to do it?
>>
>
> afaik \include doesn't work in LaTeX headers; you'll have to use \input
> there.
>
> Could you try to use \input?
>
> Best regards
> Robert

  reply	other threads:[~2015-05-28  9:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27 13:02 org-preview-latex-fragment ignores \includes in the LATEX_HEADER Stefan Otte
2015-05-27 13:37 ` Robert Klein
2015-05-28  9:21   ` Stefan Otte [this message]
2015-05-28 16:09 ` Nick Dokos
2015-05-29  7:44 ` Eric S Fraga

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='CAFync2gQQ9+cyfVSbMneGiu0ZJkBpJRbV=hq0hFUQZ=Gxhhezw@mail.gmail.com' \
    --to=stefan.otte@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=roklein@roklein.de \
    /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).