emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: change the latex header per subtree
Date: Wed, 14 Nov 2012 23:20:55 +0100	[thread overview]
Message-ID: <874nkr6d2w.fsf@gmail.com> (raw)
In-Reply-To: <87a9ukymd1.fsf@Rainer.invalid> (Achim Gratz's message of "Wed, 14 Nov 2012 21:12:58 +0100")

Achim Gratz <Stromeko@nexgo.de> writes:

> Speaking of which, couldn't this be made easier?  There's only one
> org-export-latex-packages-alist and if you're trying to use very
> different LaTeX classes you'll end up specifying [NO-DEFAULT-PACKAGES]
> and then copying a lot of \usepackage stuff around.

So what? You define your latex classes once in your configuration
variable, and you're all set. That doesn't sound that bad.

> If it was possible to give an argument to [PACKAGES] (default, header,
> <custom>), then there would be no need for [NO-PACKAGES] and
> [DEFAULT-PACKAGES] and one yould use several sets of package
> definitions in multiple class definitions. It would be especially neat
> if there was a pendant to LATEX_HEADER that would allow to specify
> additional package collections on the fly.

So, you may to make it easier by providing an even more complex
machinery? ;) IMO, the current system is good enough for the job, even
if the initial step introduces a lot of duplicate lines.

Also, if you want to add package collections, you may include
a header-only file in your class, I guess.


Nicolas Goaziou

  reply	other threads:[~2012-11-14 22:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12 12:39 change the latex header per subtree Andreas Leha
2012-11-12 17:25 ` Suvayu Ali
2012-11-14 14:10 ` Nicolas Goaziou
2012-11-14 20:12   ` Achim Gratz
2012-11-14 22:20     ` Nicolas Goaziou [this message]
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=874nkr6d2w.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=Stromeko@nexgo.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).