LaTeX: better workaround for a Pygments LaTeXFormatter issue (with Pygments up to 2.7.4) #8879
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #8874
Feature or Bugfix
Relates
The upstream Pygments issue is fixed in their master branch for next release (current is 2.7.4).
So this tests for Pygments version and applies the fix only if needed.
Previously the Sphinx fix corrected the line spacing issue (which is infrequent because one has to use a Pygments style which utilizes "border" for some tokens and a lexer which produces these token types; this is case for pygments style 'manni' in combination with the diff lexer, see pygments/pygments#1708), but in a way overwriting the style specification. This PR does it better in a way obeying the style, and it moves the fix to better location away from sphinx.sty.