This sets the subtype to the filename, which means that you can suppress
warnings for individual paths.
For example for the following warning:
```
path/to/file.rst:5547: WARNING: duplicate label path/to/file:label, other instance in /path/to/file.rst
```
You would add this to `config.py` to suppress all warnings:
```python
extensions = [
'sphinx.ext.autosectionlabel',
]
autosectionlabel_prefix_document = True
suppress_warnings = [
'autosectionlabel.*',
]
```
To suppress warnings for the individual file path you would do:
```python
suppress_warnings = [
'autosectionlabel.path/to/file',
]
```
Fixes: https://github.com/sphinx-doc/sphinx/issues/6371
- We recently hit an issue where we expected the MathJax extension to
work with the default MathJax markup. Obviously that shouldn't be
the case (since then other formats couldn't use the math), but it
can't hurt to include a hint.
- Link from the math HTML extension page to the relevant
roles/directives.
- Also make it explicit that MathJax has a default, and that it's an
external resource that will be dynamically linked.
The documentation now correctly describes the behavior of the ``parts``
option in an inheritance-diagram directive: it gives the number of parts
that are *kept* not dropped. The option now also accepts negative
values, which drops parts from the left (which is the what the
documentation incorrectly claimed the option would do for positive
values)
As a form of testing of the new functionality, the documentation for the
inheritance_diagram extension now includes a section "Examples" that
demonstrate the different possibilities. This would fail to build
without the patch.
Closes#4872
The documentation now correctly describes the behavior of the ``parts``
option in an inheritance-diagram directive: it gives the number of parts
that are *kept* not dropped. The option now also accepts negative
values, which drops parts from the left (which is the what the
documentation incorrectly claimed the option would do for positive
values)
As a form of testing of the new functionality, the documentation for the
inheritance_diagram extension now includes a section "Examples" that
demonstrate the different possibilities. This would fail to build
without the patch.
Closes#4872
