emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jeremie Juste <jeremiejuste@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: multiple EXPORT_LATEX_HEADER lines
Date: Fri, 12 Jun 2020 18:24:15 +0200	[thread overview]
Message-ID: <87d064fe1c.fsf@gmail.com> (raw)
In-Reply-To: <87mu58mipx.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Fri, 12 Jun 2020 16:01:14 +0100")

> I am not sure I understand your question.  Sorry.
You read my mind.
> 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 is exactly what I was referring to. If the behavior of
:EXPORT_LATEX_HEADER: and :EXPORT_LATEX_HEADER:+ and all the property
keys with a (+) prefix is to collate the line then it is the expected behavior.

Then keys such as :EXPORT_LATEX_HEADER: might be misleading for the
user as he may want to use multiple line header.

One solution might be to add another suffix say :EXPORT_LATEX_HEADER++:
to generate multiple lines during the export. But I'm must quickly add that I
don't have the knowledge to do it neither to  understand the implication
of this change.

Best regards,

> (setq message-citation-line-format "On %A, %e %b %Y at %R, %N wrote:")
Many thanks for the info. I was also given this precious reference:
(info "(sc) What Supercite Does")

  reply	other threads:[~2020-06-12 16:25 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 [this message]
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

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=87d064fe1c.fsf@gmail.com \
    --to=jeremiejuste@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).