From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Fabrice Popineau <fabrice.popineau@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: EXPORT_LATEX_HEADER property
Date: Thu, 03 Mar 2016 16:49:27 +0100 [thread overview]
Message-ID: <8737s7pnnc.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAFgFV9P1D7qkVeqFCx7Jc_vY12UnLDfryKd7QAEcjhsnwb+LAw@mail.gmail.com> (Fabrice Popineau's message of "Thu, 3 Mar 2016 12:58:31 +0100")
Fabrice Popineau <fabrice.popineau@gmail.com> writes:
> In org reference, 12.7.2, it is said that:
>
> ‘LATEX_HEADER’
> Arbitrary lines added to the preamble of the document, before the ‘hyperref’
> settings. The location can be controlled via org-latex-classes.
>
> Note the plural to lines. How can several lines be specified? AFAICS, if I
> do :
>
> :EXPORT_LATEX_HEADER: \usepackage{mathptmx} % rm & math
> :EXPORT_LATEX_HEADER: \usepackage[scaled=0.90]{helvet} % ss
>
> The second line will take precedence over the first one.
The manual reference is about keywords, i.e, #+LATEX_HEADER:. You are
using properties. The two are slightly different.
In particular, each value from a #+LATEX_HEADER keyword becomes a new
line whereas new values from properties replace the old ones (hence the
PROP+ syntax).
Long story short: if you want multiple lines, use keywords. There is no
support in multi lines properties in Org. Moreover, the use cases are
sufficiently rare that I don't even think it is worth implementing. In
any case, such implementation should preserve the equivalence explained
before.
Regards,
next prev parent reply other threads:[~2016-03-03 15:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 11:02 EXPORT_LATEX_HEADER property Fabrice Popineau
2016-03-03 11:26 ` Nicolas Goaziou
2016-03-03 11:58 ` Fabrice Popineau
2016-03-03 15:49 ` Nicolas Goaziou [this message]
2016-03-03 18:58 ` Eric S Fraga
2016-03-03 19:17 ` Fabrice Popineau
2016-03-03 21:16 ` Eric S Fraga
2016-03-03 16:16 ` Eric S Fraga
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=8737s7pnnc.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=fabrice.popineau@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 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).