From: Nicolas Goaziou <email@example.com>
To: Rasmus <firstname.lastname@example.org>
Subject: Re: [ox] possible to modify org-export-document-properties OTG
Date: Sun, 22 Mar 2015 00:10:52 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (email@example.com's message of "Wed, 18 Mar 2015 17:42:01 +0100")
Rasmus <firstname.lastname@example.org> writes:
> Nicolas Goaziou <email@example.com> writes:
>> Document properties are keywords where `org-element-context' is allowed
>> to return an object. It doesn't make sense to add random keywords
>> specific to some export back-ends to the list.
> I think something like SUBJECT in ox-koma-letter makes sense.
It seems we are failing to communicate.
I have nothing against SUBJECT being parsed in "ox-koma-letter".
However, `org-element-document-properties' are keywords expected to be
parsed in _every_ export back-end. This is not for SUBJECT.
>> At some point, I thought about adding a `parsed' behaviour to
>> `org-export-options-alist' as a shortcut.
> Presumably you'd want to be able to toggle it for elements of
I mean to use `parsed' at the BEHAVIOR position in
`org-export-options-alist' entries. So, obviously, this is triggered per
> I don't understand why an export setting would affect an element
> interpretation such as org-element-map. Probably I have something
> different in mind than you.
If you map over a parse tree, e.g., looking for bold objects, it is
a bit tricky to tell `org-element-map' that SUBJECT is no longer
a regular keyword but now possibly contains objects.
OTOH, we can consider that SUBJECT is still a regular keyword, and that
the property the keyword sets (e.g., :koma-letter-subject) contains the
In this case, it is no longer ambiguous for `org-element-map' and al.,
and `parsed' becomes an interesting shortcut.
next prev parent reply other threads:[~2015-03-21 23:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 0:58 [ox] possible to modify org-export-document-properties OTG Rasmus
2015-03-17 8:25 ` Nicolas Goaziou
2015-03-18 16:42 ` Rasmus
2015-03-21 23:10 ` Nicolas Goaziou [this message]
2015-03-22 0:06 ` Rasmus
2015-03-22 1:06 ` Nicolas Goaziou
2015-03-22 1:34 ` Rasmus
2015-03-22 14:12 ` Nicolas Goaziou
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).