* mentioning EXPORT_LATEX_HEADER in the latex header info node
@ 2017-11-13 15:41 Alan Schmitt
2017-11-16 21:00 ` Nicolas Goaziou
0 siblings, 1 reply; 4+ messages in thread
From: Alan Schmitt @ 2017-11-13 15:41 UTC (permalink / raw)
To: emacs-orgmode
[-- Attachment #1: Type: text/plain, Size: 340 bytes --]
Hello,
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.
Best,
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 --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: mentioning EXPORT_LATEX_HEADER in the latex header info node
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
0 siblings, 1 reply; 4+ messages in thread
From: Nicolas Goaziou @ 2017-11-16 21:00 UTC (permalink / raw)
To: Alan Schmitt; +Cc: emacs-orgmode
Hello,
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?
Regards,
--
Nicolas Goaziou
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: mentioning EXPORT_LATEX_HEADER in the latex header info node
2017-11-16 21:00 ` Nicolas Goaziou
@ 2017-11-17 9:33 ` Alan Schmitt
2017-11-17 11:48 ` Kaushal Modi
0 siblings, 1 reply; 4+ messages in thread
From: Alan Schmitt @ 2017-11-17 9:33 UTC (permalink / raw)
To: Nicolas Goaziou; +Cc: emacs-orgmode
[-- 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 --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: mentioning EXPORT_LATEX_HEADER in the latex header info node
2017-11-17 9:33 ` Alan Schmitt
@ 2017-11-17 11:48 ` Kaushal Modi
0 siblings, 0 replies; 4+ messages in thread
From: Kaushal Modi @ 2017-11-17 11:48 UTC (permalink / raw)
To: Alan Schmitt; +Cc: emacs-org list, Nicolas Goaziou
[-- Attachment #1: Type: text/plain, Size: 850 bytes --]
On Fri, Nov 17, 2017, 4:35 AM Alan Schmitt <alan.schmitt@polytechnique.org>
wrote:
>
> 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)?
>
I haven't used #+EXPORT_FILE_NAME *keyword* when exporting files because
the exported file name base name is taken from the Org file base name.
But I have used that as a :EXPORT_FILE_NAME: *property* in subtrees many
times, when doing subtree scoped exports, and it works great :) For subtree
exports, it's kind of mandatory to set that property if you want to export
different subtrees from the same Org file to different files.
> --
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 1439 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2017-11-17 11:49 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2017-11-17 11:48 ` Kaushal Modi
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).