fix asciidoc code annotations following pandoc update#12442
Merged
Conversation
Member
Yes, that follows what we usually do, thanks. |
So that we would have found #12441 earlier
cderv
force-pushed
the
fix/asciidoc-code-annotate
branch
from
9d4cb62 to
569135a
Compare
Member
Author
|
This solves #12441 and is part of Merging this one. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
rawInlinenow that pandoc 3.6.2 escape<with++<fix #12441 - see more details there.
No changelog added because this was only introduced following Pandoc update for 1.7?