Rasmus ras...@gmx.us writes:
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
(:subject SUBJECT nil nil parsed)
`parsed' behavior implies `space' anyway, since we're talking about
secondary strings.
Is that always the case? I guess..
There are only two ways to look at it: either it
Rasmus ras...@gmx.us writes:
Nicolas Goaziou m...@nicolasgoaziou.fr 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
Nicolas Goaziou m...@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
Rasmus ras...@gmx.us writes:
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)
(:subject SUBJECT nil nil parsed)
`parsed' behavior implies `space' anyway, since we're
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Rasmus ras...@gmx.us writes:
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)
(:subject SUBJECT nil nil parsed)
Nicolas Goaziou m...@nicolasgoaziou.fr 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.
Hello,
Rasmus ras...@gmx.us writes:
Is it possible to modify or extend org-export-document-properties on the
go? And would it be OK?
`org-export-document-properties' is a defconst, which is computed from
`org-element-document-properties', also a defconst. So, no, it
isn't meant for that.
