[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: multipage html output
From: |
Ihor Radchenko |
Subject: |
Re: multipage html output |
Date: |
Tue, 23 Jul 2024 17:13:56 +0000 |
Orm Finnendahl <orm.finnendahl@selma.hfmdk-frankfurt.de> writes:
>> If you think that multipage export should use a different set of
>> options, we need to implement it differently.
>
> Is that a semantic problem so we need to implement an option like
> :always-collect-headline-numbering instead of :multipage in
> org-export-numbered-headline-p? If on the other hand we define a
> replacement of org-export--collect-headline-numbering, we also have to
> do so for all functions up the stack, like org-export--annotate-info
> and org-export--collect-tree-properties. Or what did you have in mind?
What I had in mind if using backend-specific :filter-options.
If a backends needs to enable headline numbering unconditionally, when
:multipage is used, it can install :filter-options filter that will set
:section-numbers to t.
Does it make sense?
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
- Re: multipage html output, (continued)
- Re: multipage html output, Orm Finnendahl, 2024/07/26
- Re: multipage html output, Ihor Radchenko, 2024/07/27
- Re: multipage html output, Orm Finnendahl, 2024/07/27
- Re: multipage html output, Ihor Radchenko, 2024/07/23
- Re: multipage html output, Orm Finnendahl, 2024/07/23
- Re: multipage html output, Ihor Radchenko, 2024/07/23
- Re: multipage html output, Orm Finnendahl, 2024/07/23
- Re: multipage html output,
Ihor Radchenko <=
- Re: multipage html output, Orm Finnendahl, 2024/07/23
Re: multipage html output, Rudolf Adamkovič, 2024/07/03
Re: multipage html output, Pedro Andres Aranda Gutierrez, 2024/07/06
Re: Re: multipage html output, Pedro Andres Aranda Gutierrez, 2024/07/07