emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: change the latex header per subtree
Date: Mon, 12 Nov 2012 13:39:10 +0100	[thread overview]
Message-ID: <87ip9b9es1.fsf@med.uni-goettingen.de> (raw)

Hi all,

I'd like to change the LaTeX header per subtree.  Is that possible?

Use case:  I have two documents that I want to export from a single
orgmode file.  Each in its own subtree.  One of them should use the
endfloat package, the other should not.

Like this:
| * Document 1
| #+LATEX_HEADER: \usepackage[nomarkers,nolists,heads,tablesfirst]{endfloat}
| * Document 2
| * Code


             reply	other threads:[~2012-11-12 12:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12 12:39 Andreas Leha [this message]
2012-11-12 17:25 ` change the latex header per subtree Suvayu Ali
2012-11-14 14:10 ` Nicolas Goaziou
2012-11-14 20:12   ` Achim Gratz
2012-11-14 22:20     ` Nicolas Goaziou
2012-11-15 18:37       ` Achim Gratz
2012-11-15 22:24         ` Nicolas Goaziou
2012-11-16 19:24           ` Achim Gratz
2012-11-15  8:51   ` Andreas Leha

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=87ip9b9es1.fsf@med.uni-goettingen.de \
    --to=andreas.leha@med.uni-goettingen.de \
    --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).