emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: Eric S Fraga <e.fraga@ucl.ac.uk>, Jeremie Juste <jeremiejuste@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: multiple EXPORT_LATEX_HEADER lines
Date: Sat, 13 Jun 2020 17:02:33 +0200	[thread overview]
Message-ID: <877dwb101i.fsf@m4x.org> (raw)
In-Reply-To: <87mu58mipx.fsf@ucl.ac.uk>

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

Hello,

On 2020-06-12 16:01, Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> The snippet from the OP will collate all three LaTeX header lines into a
> single line on export, which is expected in terms of org's
> behaviour.  This appears to cause problems with LaTeX, which is maybe
> expected or not; I don't know what LaTeX expects when working in @
> letter mode as I've seldom (if ever?) had to redefine @ variables.

This is the crux of the issue: there does not seem to be any way to
generate a multi-line header. And this causes problems with LaTeX.

There are two workarounds for this that I know of: put the latex in some
other file and \input it, or use a dedicated file and use multiple
#+LATEX_HEADER. I ended up doing it that way.

Thanks,

Alan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  parent reply	other threads:[~2020-06-13 15:05 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 [this message]
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

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=877dwb101i.fsf@m4x.org \
    --to=alan.schmitt@polytechnique.org \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=jeremiejuste@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).