From: Jambunathan K <kjambunathan@gmail.com>
To: "François Allisson" <francois@allisson.co>
Cc: Org mode <emacs-orgmode@gnu.org>
Subject: Re: new exporter - subtree export and a few keywords
Date: Tue, 18 Dec 2012 17:25:05 +0530 [thread overview]
Message-ID: <874njj8tie.fsf@gmail.com> (raw)
In-Reply-To: <m1k3sfek73.fsf@macdroit605e.unil.ch> ("François Allisson"'s message of "Tue, 18 Dec 2012 11:19:44 +0100")
François Allisson <francois@allisson.co> writes:
> Dear org-mode users and developers,
>
> The following concerns Nicolas' new exporter.^
>
> I am totally seduced by the concept of export by subtree, and the
> possibility to use properties to set the export options and parameters
> (i.e. :EXPORT_TITLE:, :EXPORT_OPTIONS:, :EXPORT_LATEX_HEADER:, etc.).
>
> I am wondering if all that could be done by exporting the whole document
> can be done with exporting by subtree. So far, I am concerned by the
> following keywords, that I used (here with examples):
>
>
> #+LANGUAGE: ru
>
>
> and
>
>
> #+BIND: org-e-latex-title-command ""
> Can these be achieved by subtree export, or using another trick I am not
> aware of?
No answer. But I will share a trick.
Good way to answer such questions is to do this:
M-x find-library RET org-export RET
C-s EXPORT_
and with couple of more C-s es you will end up with something like.
,---- C-h v org-export-options-alist
| KEYWORD is a string representing a buffer keyword, or nil. Each
| property defined this way can also be set, during subtree
| export, through an headline property named after the keyword
| with the \"EXPORT_\" prefix (i.e. DATE keyword and EXPORT_DATE
| property).
`----
> Best,
> François
>
>
--
next prev parent reply other threads:[~2012-12-18 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 10:19 new exporter - subtree export and a few keywords François Allisson
2012-12-18 11:55 ` Jambunathan K [this message]
2012-12-21 10:06 ` François Allisson
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=874njj8tie.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=francois@allisson.co \
/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).