From: Ken Mankoff <mankoff@gmail.com>
To: Jacob Gerlach <jacobgerlach@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Include lengthy LaTeX in export preamble
Date: Sun, 27 Jul 2014 22:08:07 -0400 [thread overview]
Message-ID: <m2r4162pwm.fsf@gmail.com> (raw)
In-Reply-To: <CAA6UvuHg2mT7_VtC2TPXmALp9vAuPN3y8=sV7iz__UqCAbzcbQ@mail.gmail.com>
Hi Jacob,
#+LATEX_HEADER: does work on export (when else would it work?)
I think I recall a space between the ":" and the LaTeX command is
needed. Do you have one?
For more ideas on how to have lengthy custom headers, see thread here:
https://lists.gnu.org/archive/html/emacs-orgmode/2014-06/msg00734.html
and links therein. There are three general approaches:
1) Make a custom class file and include that, either in your init file
or in the Org file.
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
`----
3) Implement a patch or pester developers to create a third simpler
solution.
Good luck,
-k.
* On 2014-07-27 at 21:00, Jacob Gerlach wrote:
> I have a lengthy command customization that I want to include in LaTeX
> export. Since it must appear in the preamble,
> #+BEGIN_LATEX
> ...
> #+END_LATEX
>
> didn't work. I had to prepend
> #+LATEX_HEADER:
> 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?
>
> Thanks,
> Jake
next prev parent reply other threads:[~2014-07-28 2:11 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 [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2r4162pwm.fsf@gmail.com \
--to=mankoff@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jacobgerlach@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.