emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Fabrice Popineau <fabrice.popineau@supelec.fr>
To: Ken Mankoff <mankoff@gmail.com>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org,
	Sebastien Vauban
	<public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.org>,
	Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: BEGIN_LATEX_HEADER [cont]
Date: Fri, 20 Jun 2014 13:52:26 +0200	[thread overview]
Message-ID: <CAFgFV9O07jaFPvFJXHpiBVN9H-T8nK9C2zhRRkRAPf-bgENc6w@mail.gmail.com> (raw)
In-Reply-To: <m2simz96de.fsf@gorgonzola.lan>

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

2014-06-20 13:17 GMT+02:00 Ken Mankoff <mankoff@gmail.com>:

> On 2014-06-20 at 04:50, Nicolas Goaziou wrote:
> > I suggest to use existing solutions instead: configure
> > `org-latex-classes'.
>
> I'm all for using existing solutions, but cannot see how I might use
> this to easily customize export differently for different documents when
> large amounts of LaTeX preamble code is being used.
>

I for long have defined my own LaTeX class (fp.cls file). It is quite easy
to handle options in there.
Now I use it in place of article or beamer etc.

\documentclass[slides]{fp}

for a beamer org document

\documentclass[exam]{fp}

for a pdf exam document


and so on.

I don't think that it is very effective to store a huge amount of TeX code
in org documents.
You end up in cuting/pasting these headers lines in each line.


My $0.02

Fabrice

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

next prev parent reply	other threads:[~2014-06-20 11:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-19 23:37 BEGIN_LATEX_HEADER [cont] Ken Mankoff
2014-06-19 23:48 ` Aaron Ecay
2014-06-20  7:51   ` Sebastien Vauban
2014-06-20  8:50     ` Nicolas Goaziou
2014-06-20 11:17       ` Ken Mankoff
2014-06-20 11:52         ` Fabrice Popineau [this message]
2014-06-20 12:11         ` Nicolas Goaziou
2014-06-21  5:43           ` Aaron Ecay
2014-06-21  8:16             ` Nicolas Goaziou
2014-06-22  0:42               ` Aaron Ecay
2014-06-22  2:00                 ` [ANN] ox-extras (was: BEGIN_LATEX_HEADER [cont]) Aaron Ecay
2014-06-22 22:07                   ` [ANN] ox-extras Rasmus
2014-06-22 22:08                     ` Rasmus
2014-06-23 19:57                   ` Nicolas Goaziou
2014-06-23 20:29                     ` Thomas S. Dye
2014-06-22  2:19                 ` BEGIN_LATEX_HEADER [cont] Ken Mankoff
2014-06-22  9:36                   ` Nicolas Goaziou
2014-06-22  9:35                 ` Nicolas Goaziou

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

  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=CAFgFV9O07jaFPvFJXHpiBVN9H-T8nK9C2zhRRkRAPf-bgENc6w@mail.gmail.com \
    --to=fabrice.popineau@supelec.fr \
    --cc=mail@nicolasgoaziou.fr \
    --cc=mankoff@gmail.com \
    --cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
    --cc=public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.org \
    /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

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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