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
Describe your proposed improvement and the problem it solves.
The current method of defining fenced code attributes breaks syntax highlighting in git hosting sites (tested in github, codeberg).
already work in pandoc, but additional attributes are not parsed as attributes, they are parsed as part of the codeblock text.
Describe alternatives you've considered.
The pandoc-entangled repository works around this problem by specifying a custom link before code blocks. This is definitely not ideal, because it breaks write format interchangeability within pandoc.
The text was updated successfully, but these errors were encountered:
This allows the combination of the fenced code block shortcut form with
attributes:
```haskell {.class #id}
```
The code syntax class will be combined with the attribute classes.
This syntax allows for more intuitive writing and for better compatibility
with other Markdown parsers such as GitHub or Codeberg.
This allows the combination of the fenced code block shortcut form with
attributes:
```haskell {.class #id}
```
The code syntax class will be combined with the attribute classes.
This syntax allows for more intuitive writing and for better compatibility
with other Markdown parsers such as GitHub or Codeberg.
Describe your proposed improvement and the problem it solves.
The current method of defining fenced code attributes breaks syntax highlighting in git hosting sites (tested in github, codeberg).
For example:
renders as
I propose a minor change to the syntax that is already partially supported:
Which renders as:
Code blocks of the form:
already work in pandoc, but additional attributes are not parsed as attributes, they are parsed as part of the codeblock text.
Describe alternatives you've considered.
The pandoc-entangled repository works around this problem by specifying a custom link before code blocks. This is definitely not ideal, because it breaks write format interchangeability within pandoc.
The text was updated successfully, but these errors were encountered: