Re: Do not inherit unnumbered property: help needed

[Nicolas Goaziou <mail@nicolasgoaziou.fr>]

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:


> Akater <nuclearspace@gmail.com> writes:
>
>> I got an impression that UNNUMBERED's children get cut off prior to
>> what user can do,
>
> UNNUMBERED headings are not cut off, at least not by "ox.el".
>
>> hence writing a simple backend won't help, and I'll have to patch org
>> (ox) source. Do you know for sure I'm wrong?
>
> I'm quite certain you're wrong.
>
>> That's what I asked for
>> originally---which function is responsible for excluding unnumbered's
>> children from exported entries.
>
> Three functions actually check UNNUMBERED properties:
>
> - org-export-numbered-headline-p
> - org-export-collect-headlines
> - org-export-excluded-from-toc-p
>
> You can ignore the last two because it's a special case (when value is
> "notoc").
>
> So, if you want to control UNNUMBERED property, just don't trust
> `org-export-numbered-headline-p', or any function calling it.

On second thought, we might as well give more flexibility to the users,
that is, as long as one doesn't expect to get something meaningful from
every UNNUMBERED combination.

It is now possible to change UNNUMBERED status mid-tree, like any other
inherited property.

Regards,