Syntax highlighting for {=language} ... code blocks
#369
Conversation
This file contains 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
|
@alerque Does this stand a chance to being merged some day? It's been bugging me for ages |
|
@Konfekt I'm pretty sure the merge I did to resolve the conflict is now a regression. Can you do a PR review and suggest an edit that applies the changes from 72d9553 on top of the other changes that just came in? I'm happy to get this merged, it just fell off my radar and I don't have time to test the changes vs. regression of whatever else was changed here. |
user202729
force-pushed
the
patch-syntax-highlighting
branch
from
6cf1671 to
947655f
Compare
|
Seems like it's working now. That said do make sure |
alerque
approved these changes
Mar 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #367.
Simple modification of the current regex to detect
```{.language} ... ```.