You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The custom title style for subsections uses the numbering for the section instead of the subsection, I believe this is a mistake.
It seems from this article that the intended usage is to use ## as your top section in markdown so the subsection will always be the top section for numbering however, this means that if you use numbered sections (I myself have used # in markdown to create sections) or subsubsection, the numbering looks weird.
Example
For example if I have the following quarto document:
---
title: Title
format: PrettyPDF-pdf
number-sections: TRUE
---
# Example section
## Example subsection
### Example subsubsection
It produces the following output:
Note that both the section and the subsection has the number 1. The subsection should instead say 1.1.
Hacky fix
For now, my fix in my document has been to put the following in the YAML header of my document:
Introducing this to the above example yields the correct output as you can see below:
Actions
I will submit a pull request to fix this shortly. Although I recognise this could be a breaking change for some people who only use ## and assumed this is fine for numbering purposes.
The text was updated successfully, but these errors were encountered:
Outline of the problem
The custom title style for subsections uses the numbering for the section instead of the subsection, I believe this is a mistake.
It seems from this article that the intended usage is to use
##
as your top section in markdown so the subsection will always be the top section for numbering however, this means that if you use numbered sections (I myself have used#
in markdown to create sections) or subsubsection, the numbering looks weird.Example
For example if I have the following quarto document:
It produces the following output:
Note that both the section and the subsection has the number 1. The subsection should instead say 1.1.
Hacky fix
For now, my fix in my document has been to put the following in the YAML header of my document:
Introducing this to the above example yields the correct output as you can see below:
Actions
I will submit a pull request to fix this shortly. Although I recognise this could be a breaking change for some people who only use ## and assumed this is fine for numbering purposes.
The text was updated successfully, but these errors were encountered: