emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: multiple EXPORT_LATEX_HEADER lines
Date: Tue, 16 Jun 2020 14:03:23 -0400	[thread overview]
Message-ID: <87d05yubv8.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: 87pna4n0s6.fsf@gmail.com

Dominik Schrempf <dominik.schrempf@gmail.com> writes:

> Hello,
> are you looking for, e.g.,
> #+latex_header: \addbibresource{bibliography.bib}
> #+latex_header_extra: do some stuff
> #+latex_header_extra: and even more
> I don't use the EXPORT keyword at the beginning, I am not sure if it is needed.
> Best,
> Dominik

Just as a clarification: the "_extra" here does not mean "append to previous value".

The only difference between "#+latex_header: " and #+latex_header_extra: " is
that anything specified in the former is *also* used when constructing the header
for the LaTeX file for previewing LaTeX fragments, whereas anything specified in the
latter is only used when exporting: it is not used when previewing.


    (info "(org) LaTeX header and sectioning")

which says:

|    The LaTeX export back-end appends values from ‘LATEX_HEADER’ and
| ‘LATEX_HEADER_EXTRA’ keywords to the LaTeX header.  The docstring for
| ‘org-latex-classes’ explains in more detail.  Also note that LaTeX
| export back-end does not append ‘LATEX_HEADER_EXTRA’ to the header when
| previewing LaTeX snippets (see *note Previewing LaTeX fragments::).

and the code in ox-latex.el:org-latex-make-preamble.

> Alan Schmitt <alan.schmitt@polytechnique.org> writes:
>> Hello,
>> I would like to have a multi-line export header when exporting a
>> subtree. I tried this:
>> :EXPORT_LATEX_HEADER: \makeatletter
>> :EXPORT_LATEX_HEADER+: \@setplength{refvpos}{\useplength{toaddrvpos}}
>> :EXPORT_LATEX_HEADER+: \makeatother
>> The problem is that it's exported on a single line, and as such it does
>> not work. Is there a way to have the multiple properties exported as
>> multiple lines, or to specify in the property there is a line break?
>> Thanks,
>> Alan


"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler

      parent reply	other threads:[~2020-06-16 18:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-12  8:08 multiple EXPORT_LATEX_HEADER lines Alan Schmitt
2020-06-12  8:31 ` Dominik Schrempf
2020-06-12  8:37   ` Alan Schmitt
2020-06-12 12:01     ` Jeremie Juste
2020-06-12 12:30       ` Eric S Fraga
2020-06-12 14:47         ` Jeremie Juste
2020-06-12 15:01           ` Eric S Fraga
2020-06-12 16:24             ` Jeremie Juste
2020-06-13 15:02             ` Alan Schmitt
2020-06-15  9:20               ` Eric S Fraga
2020-06-16  8:46                 ` Alan Schmitt
2020-06-16  9:55                   ` Eric S Fraga
2020-06-16 18:03   ` Nick Dokos [this message]

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=87d05yubv8.fsf@alphaville.usersys.redhat.com \
    --to=ndokos@gmail.com \
    --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).