From: Kaushal Modi <kaushal.modi@gmail.com>
To: Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: emacs-org list <emacs-orgmode@gnu.org>,
Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: mentioning EXPORT_LATEX_HEADER in the latex header info node
Date: Fri, 17 Nov 2017 11:48:53 +0000 [thread overview]
Message-ID: <CAFyQvY3tapbrGR-ZX51-0Sh-tcWsmA-VUbwiKczdNuHBAJPPNw@mail.gmail.com> (raw)
In-Reply-To: <m2o9o16ygy.fsf@polytechnique.org>
[-- 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 --]
prev parent reply other threads:[~2017-11-17 11:49 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
2017-11-17 11:48 ` Kaushal Modi [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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFyQvY3tapbrGR-ZX51-0Sh-tcWsmA-VUbwiKczdNuHBAJPPNw@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.