Rasmus writes:
> Nicolas Goaziou 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 can only contain
obj
Nicolas Goaziou writes:
> Rasmus 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 i
Rasmus 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 talki
Nicolas Goaziou 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
Rasmus writes:
> Nicolas Goaziou 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
Nicolas Goaziou 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. But what
I'm reall
Hello,
Rasmus 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.
Document prope
Hi,
Is it possible to modify or extend org-export-document-properties on the
go? And would it be OK? From the docstring of ox-version version of
document-properties I would say 'yes'. I'm not sure when reading the
docstrig of org-element version.
Or should org-element-parse-secondary-string be
