From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: mentioning EXPORT_LATEX_HEADER in the latex header info node
Date: Fri, 17 Nov 2017 10:33:49 +0100 [thread overview]
Message-ID: <m2o9o16ygy.fsf@polytechnique.org> (raw)
In-Reply-To: <87o9o2ueex.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Thu, 16 Nov 2017 22:00:54 +0100")
[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]
On 2017-11-16 22:00, Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Alan Schmitt <alan.schmitt@polytechnique.org> writes:
>
>> The LaTeX header and sectioning structure info node talks about
>> LATEX_HEADER and LATEX_HEADER_EXTRA. Maybe it could mention the EXPORT
>> version as well, as is done for the LATEX_CLASS_OPTION.
>
> Since adding "EXPORT_" prefixed version of all keywords could be
> overwhelming, I'd rather do it the other way and remove
> EXPORT_LATEX_CLASS_OPTION reference. We could consider that all is said
> in the last paragraph of (info "(org)Export settings").
>
> WDYT?
It makes sense. Reading the text there, I'm a bit surprised:
For example, `DATE' and `EXPORT_FILE_NAME' keywords become,
respectively, `EXPORT_DATE' and `EXPORT_FILE_NAME'.
Is the `EXPORT_FILE_NAME' a real example (i.e., a node property that has
a global and subtree meaning with the same name)?
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
Monthly Athmospheric CO₂, Mauna Loa Obs. 2017-10: 403.64, 2016-10: 401.57
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 528 bytes --]
next prev parent reply other threads:[~2017-11-17 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 15:41 mentioning EXPORT_LATEX_HEADER in the latex header info node Alan Schmitt
2017-11-16 21:00 ` Nicolas Goaziou
2017-11-17 9:33 ` Alan Schmitt [this message]
2017-11-17 11:48 ` Kaushal Modi
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=m2o9o16ygy.fsf@polytechnique.org \
--to=alan.schmitt@polytechnique.org \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).