emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Fabrice Popineau <fabrice.popineau@gmail.com>
To: Fabrice Popineau <fabrice.popineau@gmail.com>,
	"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: EXPORT_LATEX_HEADER property
Date: Thu, 3 Mar 2016 12:58:31 +0100	[thread overview]
Message-ID: <CAFgFV9P1D7qkVeqFCx7Jc_vY12UnLDfryKd7QAEcjhsnwb+LAw@mail.gmail.com> (raw)
In-Reply-To: <87bn6vpzud.fsf@nicolasgoaziou.fr>

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

2016-03-03 12:26 GMT+01:00 Nicolas Goaziou <mail@nicolasgoaziou.fr>:

> Hello,
>
>
Hi Nicolas,


> Fabrice Popineau <fabrice.popineau@gmail.com> writes:
>
> > First, I can't find where is documented the difference between
> > :EXPORT_LATEX_HEADER:
> > and
> > :EXPORT_LATEX_HEADER+:
>
> See (info "(org) Property syntax").
>
>
I need to learn to read better because I didn't see that this paragraph was
about it:

If you want to add to the value of an existing property, append a + to the
property name.
The following results in the property var having the value “foo=1 bar=2”.
#+PROPERTY: var foo=1
#+PROPERTY: var+ bar=2



> Second, when I use several lines with
> > :EXPORT_LATEX_HEADER+:
> > they  are concatenated into a single line.
>
> Correct.
>
> > This is annoying because:
> >
> > :PROPERTIES:
> > :EXPORT_LATEX_HEADER+: \usepackage{mathptmx} % rm & math
> > :EXPORT_LATEX_HEADER+: \usepackage[scaled=0.90]{helvet} % ss
> > ...
> > :END:
> >
> > results in
> >
> > \usepackage{mathptmx} % rm & math  \usepackage[scaled=0.90]{helvet} % ss
> >
> > which is obviously unintended.
> >
> > Could it be possible to add a '\n' between those lines?
>
> Not quite what you are asking for, but couldn't you simply not comment
> each line?
>
> Yes, I can remove the comments, however, from time to time, it may be
useful to be able to comment
some \usepackage line, and I don't see how it can be done in Org, except by
killing the whole line.

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.

Thanks for your help,

Fabrice

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

  reply	other threads:[~2016-03-03 11:58 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 [this message]
2016-03-03 15:49     ` Nicolas Goaziou
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=CAFgFV9P1D7qkVeqFCx7Jc_vY12UnLDfryKd7QAEcjhsnwb+LAw@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 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).