emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jacob Gerlach <jacobgerlach@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Include lengthy LaTeX in export preamble
Date: Sun, 27 Jul 2014 21:00:31 -0400	[thread overview]
Message-ID: <CAA6UvuHg2mT7_VtC2TPXmALp9vAuPN3y8=sV7iz__UqCAbzcbQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 508 bytes --]

I have a lengthy command customization that I want to include in LaTeX
export. Since it must appear in the preamble,

didn't work. I had to prepend
to each line in order to achieve my result.

I found C-h v org-format-latex-header RET:

"The document header used for processing LaTeX fragments..."

But it seems that when the docstring says "fragments," it is not referring
to exporting.

Are there any customizations to do the same during export?


[-- Attachment #2: Type: text/html, Size: 785 bytes --]

             reply	other threads:[~2014-07-28  1:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-28  1:00 Jacob Gerlach [this message]
2014-07-28  2:08 ` Include lengthy LaTeX in export preamble Ken Mankoff
2014-07-28  2:19   ` Jacob Gerlach

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:

  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='CAA6UvuHg2mT7_VtC2TPXmALp9vAuPN3y8=sV7iz__UqCAbzcbQ@mail.gmail.com' \
    --to=jacobgerlach@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).