Hello,
Eric Schulte writes:
> Hmmm, I don't have a strong intuition here. I'm tempted to say that
> whatever the HTML export engine does would be a good starting place,
> plus any keyword explicitly set in subtree properties. I feel like this
> decision must have already been made in some othe
Nicolas Goaziou writes:
> Eric Schulte writes:
>
>> My initial thoughts are that inserting keywords *with* values while not
>> inserting empty keywords would be the most intuitive.
>
> TITLE always have a value. When not specified, it defaults to buffer's
> name.
>
> Also, what keywords? Documen
Eric Schulte writes:
> My initial thoughts are that inserting keywords *with* values while not
> inserting empty keywords would be the most intuitive.
TITLE always have a value. When not specified, it defaults to buffer's
name.
Also, what keywords? Document keywords (DATE, AUTHOR, TITLE)? Or ot
Nicolas Goaziou writes:
> Hello,
>
> Eric Schulte writes:
>
>> Specifically, the title is not taken from the current heading, and
>> subheadings are not promoted to the top level.
>
> I partly fixed this: subheadings should now get correct level.
>
Confirmed, thanks.
>
> OTOH, "ox-org" back-en
Hello,
Eric Schulte writes:
> Specifically, the title is not taken from the current heading, and
> subheadings are not promoted to the top level.
I partly fixed this: subheadings should now get correct level.
OTOH, "ox-org" back-end doesn't insert any keyword (DATE, AUTHOR,
TITLE), subtree exp
Specifically, the title is not taken from the current heading, and
subheadings are not promoted to the top level.
Export the "Example Subtree" heading in the attached example file using
the "subtree" option to demonstrate.
Thanks,
#+Title: Subtree Export Example
* Top
** Problem
I think subtree
