You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was trying to use commonmark+fenced_code_attributes and gfm+fenced_code_attributes with one of the examples from the manual, but it didn't work -- the attributes like .haskell would get lost in the output:
I ended up spending an embarrassingly long time trying to figure out what was wrong, and finally discovered that it was because commonmark and gfm have -fenced_code_attributes:
So when I used +fenced_code_attributes, it was silently being ignored. It would be much friendlier behavior to either print an error message in this situation, or allow +fenced_code_attributes to override the setting in commonmark.
The text was updated successfully, but these errors were encountered:
When this prints -fenced_code_attributes, it means that this extension will affect the format, and that it is set to disabled by default. So +fenced_code_attributesshould work.
Looks like +fenced_code_attributes+attributes does work.
(And also +attributes by itself). I need to look into this.
jgm
changed the title
Request: print a message when extension conflicts with a format, or allow extension to override
Problem with fenced_code_attributes with commonmark
Feb 13, 2021
I was trying to use
commonmark+fenced_code_attributes
andgfm+fenced_code_attributes
with one of the examples from the manual, but it didn't work -- the attributes like.haskell
would get lost in the output:The result:
I ended up spending an embarrassingly long time trying to figure out what was wrong, and finally discovered that it was because
commonmark
andgfm
have-fenced_code_attributes
:So when I used
+fenced_code_attributes
, it was silently being ignored. It would be much friendlier behavior to either print an error message in this situation, or allow+fenced_code_attributes
to override the setting incommonmark
.The text was updated successfully, but these errors were encountered: