From: Nicolas Goaziou <n.goaziou@gmail.com>
To: suvayu ali <fatkasuvayu+linux@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [ANN] Beamer back-end for org-export in contrib/
Date: Thu, 05 Jul 2012 13:56:26 +0200 [thread overview]
Message-ID: <8762a2fml1.fsf@gmail.com> (raw)
In-Reply-To: <CAMXnza3_FMVG0X2KVhKi9ih8pC2c+U70VSAqt==PJs+2CihLRg@mail.gmail.com> (suvayu ali's message of "Wed, 4 Jul 2012 18:26:46 +0200")
Hello,
suvayu ali <fatkasuvayu+linux@gmail.com> writes:
> If I understand correctly, having a buffer keyword would mean I would
> need to find and update it appropriately everytime I want to export
> something. I can live with this, but it would be great if there was
> support these export options as properties. Then all the subtree exports
> can be decoupled easily.
I agree.
Now, /every/ property set through an export keyword can also be defined
with an headline property. That property has the same name as the
keyword, with an "EXPORT_" prefix (i.e #+DATE: and :EXPORT_DATE:).
This is also true for keywords defined by back-ends (#+LATEX_CLASS:
and :EXPORT_LATEX_CLASS:).
In order to avoid confusion, I've renamed buffer keyword setting select
tags (resp. exclude tags) from EXPORT_SELECT_TAGS
(resp. EXPORT_EXCLUDE_TAGS) to SELECT_TAGS (resp. EXCLUDE_TAGS).
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2012-07-05 11:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-30 14:59 [ANN] Beamer back-end for org-export in contrib/ Nicolas Goaziou
2012-06-30 18:46 ` suvayu ali
2012-07-02 12:22 ` Nicolas Goaziou
2012-07-04 1:30 ` suvayu ali
2012-07-04 16:08 ` Nicolas Goaziou
2012-07-04 16:26 ` suvayu ali
2012-07-05 11:56 ` Nicolas Goaziou [this message]
2012-07-07 10:04 ` suvayu ali
2012-07-07 12:32 ` Nicolas Goaziou
2012-07-07 12:56 ` suvayu ali
2012-07-07 12:58 ` Nicolas Goaziou
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=8762a2fml1.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=fatkasuvayu+linux@gmail.com \
/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).