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
Is there a reason for @s generating headers exclusively with <h4>? As far as I get from the documentation, the only way to have proper (but unnumbered) subsections is using markdown's # style headers... but I need to use <h5> which may be too small...
As for numbered headers using markdown, one could use --md-compiler 'pandoc --number-section', but still, you require at least one @s in order to render code blocks, and means rendering an <h4>...
I guess I would be happy with either:
configurable @s depth, either inline or via cli
not requiring @s for rendering code
Thanks for this cool project, hope you don't get tired of my reports ;)
The text was updated successfully, but these errors were encountered:
Is there a reason for
@s
generating headers exclusively with<h4>
? As far as I get from the documentation, the only way to have proper (but unnumbered) subsections is using markdown's#
style headers... but I need to use<h5>
which may be too small...As for numbered headers using markdown, one could use
--md-compiler 'pandoc --number-section'
, but still, you require at least one@s
in order to render code blocks, and means rendering an<h4>
...I guess I would be happy with either:
@s
depth, either inline or via cli@s
for rendering codeThanks for this cool project, hope you don't get tired of my reports ;)
The text was updated successfully, but these errors were encountered: