Support fenced code blocks with 4+ backticks#933
Merged
syohex merged 2 commits intojrblevin:masterfrom Mar 1, 2026
Merged
Conversation
Previously, GFM fenced code block regexes matched exactly three backticks, causing blocks with four or more backticks to be unrecognized. This meant headers inside such blocks were incorrectly treated as document structure (outline headings, imenu entries, font-lock targets). Apply the same variable-length fence approach already used for tilde fences: match 3+ backticks in the opening/closing regexes, and dynamically require the closing fence to have at least as many backticks as the opening fence. Fixes: jrblevin#932 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
syohex
reviewed
Feb 28, 2026
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.
Summary
Fixes #932