emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Andreas Leha <andreas.leha@med.uni-goettingen.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: preview latex fragment with latex_header
Date: Wed, 06 Mar 2013 23:47:19 +0100	[thread overview]
Message-ID: <871ubsdu2w.fsf@gmail.com> (raw)
In-Reply-To: <87hakofg7g.fsf@med.uni-goettingen.de> (Andreas Leha's message of "Wed, 06 Mar 2013 21:04:03 +0100")

Hello,

Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:

> I have a beamer presentation in org-mode that contains a line like
> #+LaTeX_HEADER: \subtitle{foo}
>
> This prevents me from using 'org-preview-latex-fragment' as that one --
> naturally, as it uses the article class -- fails with
> 'Failed to create dvi file from /tmp/orgtex49760oq.tex'
> due to
>
> ,----
> | ERROR: Undefined control sequence.
> | 
> | --- TeX said ---
> | l.38 \subtitle
> `----
>
> What's the remedy here?

Interesting. I put back use of #+latex_header keywords for latex
snippets recently, but that is a double-edged sword. Overall, I'm not
sure which is the right behaviour here. Is there one, anyway?

To solve your problem, you can include your problematic header in a new
latex class instead of relying on latex_header. Another solution is to
put that latex_header line in an include file, or to generate it as
a macro.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2013-03-06 22:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06 20:04 preview latex fragment with latex_header Andreas Leha
2013-03-06 22:47 ` Nicolas Goaziou [this message]
2013-03-06 23:25   ` Andreas Leha
2013-03-07  6:14     ` Achim Gratz
2013-03-07  7:14       ` Andreas Leha
2013-03-07  8:04         ` Nicolas Goaziou
2013-03-07  8:47           ` Andreas Leha
2013-04-15 21:01           ` Bastien
2013-04-15 21:26             ` Nicolas Goaziou
2013-04-15 21:42               ` 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=871ubsdu2w.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=andreas.leha@med.uni-goettingen.de \
    --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).