From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: Parsing property drawers in subtree scope exports
Date: Thu, 06 Jul 2017 19:19:11 +0200 [thread overview]
Message-ID: <87inj57ab4.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAFyQvY0jY+2u8EYG=Z9ZM6ur2b-8ajJW0=D3r4PesJ3uDGDsAg@mail.gmail.com> (Kaushal Modi's message of "Thu, 06 Jul 2017 17:08:32 +0000")
Hello,
Kaushal Modi <kaushal.modi@gmail.com> writes:
> Thanks. That works. Just curious though.. if one specifies certain keywords
> to be exporter specific keywords in the backend definition in
> :options-alist, it is evident that those keywords are specifically for
> export. Should the requirement to have "EXPORT_" prefix before them be
> relaxed? Do you foresee things not happening right if we started doing
> that?
I do. User may not be aware of keywords defined in export back-ends. As
a consequence user-defined properties could interfere with export
specific ones. E.g., ":TITLE:" and ":EXPORT_TITLE:" could mean different
things.
> - Make use of the inbuilt EXPORT_ prefix and get rid of the "HUGO_" prefix
> I need exactly that. My idea is to have a single Org file with one subtree
> per a blog post. So each subtree will have meta data about that post, like
> data, categories, etc.
I meant that you probably need to expand the buffer in order to get the
properties. Once this is done, you can return to the original narrowing.
Regards,
--
Nicolas Goaziou 0x80A93738
prev parent reply other threads:[~2017-07-06 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-01 6:58 Parsing property drawers in subtree scope exports Kaushal Modi
2017-07-01 7:48 ` Nicolas Goaziou
2017-07-01 13:09 ` Kaushal Modi
2017-07-01 16:08 ` Nicolas Goaziou
2017-07-06 17:08 ` Kaushal Modi
2017-07-06 17:19 ` Nicolas Goaziou [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
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=87inj57ab4.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=kaushal.modi@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).