Fenced code blocks attributes in curly braces break highlighting
See original GitHub issueThanks for this package. This issue is similar to #123. I usually add fenced code blocks attributes in curly braces, as in {.bib}
. This breaks highlighting in language-markdown (gfm works fine):
Removing the curly braces fixes the issue:
I don’t insist on using curly braces, it’s just that I used to do it this way and I have a lot of older documents which I would have to readjust when I want to keep using language-markdown. Would be glad if this could be fixed.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Extended Syntax - Markdown Guide
Many Markdown processors support syntax highlighting for fenced code blocks. This feature allows you to add color highlighting for whatever language your ...
Read more >Fenced Code Blocks — Python-Markdown 3.4.1 documentation
The Fenced Code Blocks extension adds a secondary way to define code blocks, ... The attributes should be wrapped in curly braces {}...
Read more >Certain info strings on fenced code blocks break formatting ...
A workaround for this is to remove the {.cpp} info string on the first code block, but of course that destroys the code...
Read more >kramdown Syntax
The delimiting lines of a fenced code block do not support hard-wrapping. ... a hash, the ID and a closing curly bracket, the...
Read more >Markdown Syntax | YouTrack Server Documentation - JetBrains
Code Blocks Without Highlights. If you specify the language attribute inside the fenced code block as text , ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for the quick reply. This problem persists when I switch to
{.js}
.You’re right,
{js }
or{.bib }
works. Thanks for your work!