Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Discussion] Numbered sections behaviour for sphinx-external-toc #23

Open
3 tasks
mmcky opened this issue Apr 20, 2021 · 0 comments
Open
3 tasks

[Discussion] Numbered sections behaviour for sphinx-external-toc #23

mmcky opened this issue Apr 20, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@mmcky
Copy link
Member

mmcky commented Apr 20, 2021

With jupyter-book@sphinx-external-toc coming down the pipeline I have done some testing against the new syntax that allows you to specify numbered: true/false for each part in the format: jb-book schema.

This numbering flag switches numbers on and off for the part when not using sphinx-multitoc-numbering. When using sphinx-multitoc-numbering extension it works (except for the cached regression discussed below) and the numbers skip the un-numbered sections and continue at the next numbered parts.

  • Is this the desired behaviour or should be use global numbering and have numbers visible as controlled by the numbered: true/false setting?
  • maybe we could add numbered: true as a global across parts in jb-book

Cached Sphinx Builds:

You can get conditions due to the sphinx cache where switching numbered: false in some sections appear to take no affect as those pages are not rebuilt as no content has changed (according to sphinx). Perhaps when there are config keys are altered in _toc.yml we should consider those files as changed and inform sphinx?

@mmcky mmcky added the enhancement New feature or request label Apr 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant