export options and exporting subtrees

export options and exporting subtrees

[Eric Abrahamsen]

I'm not sure why I've never noticed this issue before, but...

Is it intentional that, when exporting a subtree, EXPORT_OPTIONS lines
at the top of the file (or EXPORT_OPTIONS properties on parent
headlines) are ignored? I have `org-use-property-inheritance' set to t.

I'm not wrong that that's what happens, am I? I found this a bit
surprising, but I guess I could understand why it might happen. Is it
intentional?

Thanks,
Eric

Re: export options and exporting subtrees

[Nicolas Goaziou]

Hello,

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> I'm not sure why I've never noticed this issue before, but...
>
> Is it intentional that, when exporting a subtree, EXPORT_OPTIONS lines
> at the top of the file (or EXPORT_OPTIONS properties on parent
> headlines) are ignored? I have `org-use-property-inheritance' set to t.
>
> I'm not wrong that that's what happens, am I? I found this a bit
> surprising, but I guess I could understand why it might happen. Is it
> intentional?

I don't see any reason to hard-code inheritance rules for "EXPORT_"
these properties. This is now fixed. Thank you.


Regards,

-- 
Nicolas Goaziou

Re: export options and exporting subtrees

[Eric Abrahamsen]

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Hello,
>
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> I'm not sure why I've never noticed this issue before, but...
>>
>> Is it intentional that, when exporting a subtree, EXPORT_OPTIONS lines
>> at the top of the file (or EXPORT_OPTIONS properties on parent
>> headlines) are ignored? I have `org-use-property-inheritance' set to t.
>>
>> I'm not wrong that that's what happens, am I? I found this a bit
>> surprising, but I guess I could understand why it might happen. Is it
>> intentional?
>
> I don't see any reason to hard-code inheritance rules for "EXPORT_"
> these properties. This is now fixed. Thank you.

Thanks! This seems much more intuitive to me.

E