Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Resolve documentation build warnings: Inline emphasis start-string without end-string
See original GitHub issueMattermost product documentation is written in RST, generated using Sphinx, and formatted using a Sphinx theme called ReadTheDocs.
When the documentation builds, the following common Sphinx build warning is returned:
Inline emphasis start-string without end-string
The Technical Writing team welcomes some assistance identifying what’s causing this warning in the content source files, how to resolve the warning, and how to avoid the warning altogether going forward with new content development.
VS Code-based linters and other RST format checking tools compatible with Sphinx 3.4.3 and later are also most welcome additions to our existing toolset.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
May I take this one?
Hey @cwarnermm, I am no Sphinx expert but don’t know if you have gone through this discussion already, if not, this can be of help:
https://github.com/fish-shell/fish-shell/pull/7520