Why table of contents doesn't have yet an option for disable folios on it? about sile HOT 7 CLOSED

Now you nailed it, I agree! That's the origin of my question, because for me, this header should behave just as a chapter header having no folios on the their page. I just checked for some examples, I could send you several examples of books in different languages whose ToC isn't paginated, at least not in its first page, when it happens to span through a couple of pages...

from sile.

Er. I don't get it. In most books I have, the ToC is paginated ;)
References for the contrary?

from sile.

Yeah, maybe I could have said about it being an option then...

I've a plenty of books whose toc isn't paginated and many others which they aren't.

from sile.

I've a plenty of books whose toc isn't paginated and many other which they aren't.

Then the issue is perhaps not with ToC itself, but in the section of the book where it occurs. I am sure I already mentioned front matter / main matter / back matter in some issue.¹ Whether the standard book class shall have these distinctions is debatable² but this is the real game, I think?

from sile.

BTW, this also why I believe the ToC "as-is" should just be a ToC and not have a title-like header -- one of the differences between resilient.tableofcontents and the core tableofcontents. Do one thing (a ToC), but do it well -- and let the surrounding context know whether (and how) it needs some sectioning.

from sile.

Now you nailed it,

Thanks, lol. These lines might make sense to someone else than me then:
https://github.com/Omikhleia/markdown.sile/blob/774122f15c2f5940ce5637fa5c221d3fd2e29cc8/packages/markdown/commands.lua#L744-L751

from sile.

Closing/rejecting: as discussed, folio numbering and ToC are orthogonal topics. One depends on sectioning strategies, and the other is just responsible for generating a ToC.

from sile.