emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jacob Gerlach <jacobgerlach@gmail.com>
To: Ken Mankoff <mankoff@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Include lengthy LaTeX in export preamble
Date: Sun, 27 Jul 2014 22:19:23 -0400	[thread overview]
Message-ID: <CAA6UvuEsKb1iFxRg2vE7EFfxK+EaP1dxHn4YRCG3gDN-TE2NoA@mail.gmail.com> (raw)
In-Reply-To: <m2r4162pwm.fsf@gmail.com>

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

On Sun, Jul 27, 2014 at 10:08 PM, Ken Mankoff <mankoff@gmail.com> wrote:

> Hi Jacob,
> #+LATEX_HEADER: does work on export (when else would it work?)
> Agreed. If I said otherwise it was a mistake.

2) From Aaron Ecay, put your header in a #+BEGIN_SRC latex section, and
> then run a bit of lisp to export that section, and then include the
> exported file in a #+LATEX_HEADER: \include{preamble}. This is the
> approach I use.
> ,----
> | #+begin_src emacs-lisp
> |   (org-babel-goto-named-src-block "preamble")
> |   (org-babel-tangle)
> | #+end_src
> |
> | #+name: preamble
> | #+begin_src latex :tangle preamble.tex
> |   % code goes here
> | #+end_src
> `----

This looks handy. Thanks!

My elisp ability is minimal, but if someone can point me towards where I
would look to try to create an export analogue to org-format-latex-header,
I would at least take a look and try to come up with a patch.


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

      reply	other threads:[~2014-07-28  2:19 UTC|newest]

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

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=CAA6UvuEsKb1iFxRg2vE7EFfxK+EaP1dxHn4YRCG3gDN-TE2NoA@mail.gmail.com \
    --to=jacobgerlach@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mankoff@gmail.com \


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