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
TOC not generated when using a particular Markdown header style #6791
Comments
Interestingly, the source for the markdown documentation page has a [TOC] at the start, but there is no TOC in the HTML output. |
The problem regarding the 'multiple use of section label' this was indeed the case in v1.8.15 but has been solved in the master version by the pull request #6780 based on issue #6779 and I see the TOC in both versions of the file in the master version of doxygen,. The problem with |
… header style The default for the `TOC_INCLUDE_HEADERINGS` was set to 0, for compatibility this should be 5. (Problem was observed in the doxygen documentation, chapter markdown, where the TOC was missing; alternatively in the Doxyfile the `TOC_INCLUDE_HEADERINGS` could be set to `5`,. The solution chosen is more consistent with the old situation).
I've just pushed a proposed patch, pull request #6792, regarding the |
… header style Update test
issue #6791 TOC not generated when using a particular Markdown headerstyle
Code has been integrated in master on github. |
This issue was previously marked 'fixed but not released', |
Mainly as a note to others as this is not critical and has a work-around.
Doxygen v1.8.15
Table of contents (TOC) is not generated when using the === or --- style of headers in Markdown. It does generate correctly when using the # style of headers.
Example files attached. header_style_2.md (# style) works fine, however header_style_1.md:
Issues these warnings:
As you can see from the Doxyfile, I have
TOC_INCLUDE_HEADINGS
> 0 as per #6513, which is related, but not the same problem. The extra header 1 section is needed due to bug #5892.toc_test.tar.gz
The text was updated successfully, but these errors were encountered: