From: Fabrice Popineau <fabrice.popineau@gmail.com>
To: Fabrice Popineau <fabrice.popineau@gmail.com>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: LaTeX exporter
Date: Mon, 6 Oct 2014 21:49:57 +0200 [thread overview]
Message-ID: <CAFgFV9M48sJea1PiG3X02OZnavfN9X48L3Rtj7gSoU9qJ_WzJQ@mail.gmail.com> (raw)
In-Reply-To: <87y4st6lai.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1203 bytes --]
Hi,
Maybe I wasn't clear enough.
I was thinking about an option specific of the latex exporter to expand the
document class options :
\documentclass[default_option_1, default_option_2, EXTRA_OPTIONS]{myclass}
default_option_i being taken from the org-latex-classes entry for the
current class.
Actually, LATEX_CLASS_OPTIONS overrides the whole set of options, so maybe
my suggestion is superfluous.
Regards,
2014-10-06 21:38 GMT+02:00 Nicolas Goaziou <mail@nicolasgoaziou.fr>:
> Hello,
>
> Fabrice Popineau <fabrice.popineau@gmail.com> writes:
>
> > The org-latex-classes variable handles a couple of parameters like
> > DEFAULT-PACKAGES, PACKAGES and EXTRA.
> >
> > I thing that this variable could also benefit from an EXTRA_OPTIONS
> > parameter.
> > This could allow to have a default set of options for the curent class,
> but
> > to locally
> > add a couple of options you may not always want.
> >
> > What do you think ?
>
> The OPTIONS keyword hasn't much to do with latex classes. It is handled
> at a very different level (i.e., "ox.el"). IMO, it would be confusing to
> mix them.
>
> I think you want a couple of dedicated SETUPFILE keywords.
>
>
> Regards,
>
> --
> Nicolas Goaziou
>
[-- Attachment #2: Type: text/html, Size: 1903 bytes --]
next prev parent reply other threads:[~2014-10-06 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 7:28 LaTeX exporter Fabrice Popineau
2014-10-06 19:38 ` Nicolas Goaziou
2014-10-06 19:49 ` Fabrice Popineau [this message]
2014-10-06 20:36 ` Rasmus
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=CAFgFV9M48sJea1PiG3X02OZnavfN9X48L3Rtj7gSoU9qJ_WzJQ@mail.gmail.com \
--to=fabrice.popineau@gmail.com \
--cc=emacs-orgmode@gnu.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
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.