From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [ox] possible to modify org-export-document-properties OTG
Date: Sun, 22 Mar 2015 01:06:00 +0100 [thread overview]
Message-ID: <87vbhtvqtz.fsf@gmx.us> (raw)
In-Reply-To: 877fua3q0z.fsf@nicolasgoaziou.fr
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>> I think something like SUBJECT in ox-koma-letter makes sense.
>
> It seems we are failing to communicate.
Probably I'm just slower :)
> 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.
Yep. That was why I asked if it was possible to add it on backend basis.
But the oe-parse-secondary-string is fin. Now I know.
> I mean to use `parsed' at the BEHAVIOR position in
> `org-export-options-alist' entries. So, obviously, this is triggered per
> keyword.
I /think/ that is what I would like. But I don't understand the what you
mean concretely: would you have something like:
(:subject "SUBJECT" nil nil space parsed)
I don't understand how it could replace the behavior parameter. Would it
be a cons?
> 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
> objects.
>
> In this case, it is no longer ambiguous for `org-element-map' and al.,
> and `parsed' becomes an interesting shortcut.
I agree this is a difficult problem. Personally, I think it is fine to
consider a keyword as a keyword and nothing more, and not consider content
within a keyword. However, as I recall, John had a post a while back
about mapping over bold in CAPTIONS or something like that.
I think it may be a mess to interpret content of a keyword at
org-element-map level. Consider if #+SUBJECT is interpreted with in
ox-koma-letter but not in an imaginary ox-new-letter. Would it not be
confusing?
—Rasmus
--
Dung makes an excellent fertilizer
next prev parent reply other threads:[~2015-03-22 0:06 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
2015-03-22 0:06 ` Rasmus [this message]
2015-03-22 1:06 ` Nicolas Goaziou
2015-03-22 1:34 ` Rasmus
2015-03-22 14:12 ` 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=87vbhtvqtz.fsf@gmx.us \
--to=rasmus@gmx.us \
--cc=emacs-orgmode@gnu.org \
/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).