-
-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Markdown fence syntax #281
Comments
.py
and .python
#357 was a fresh dupe from @maxschulz-COL. If anyone wants to rebase #274 and finish it off (docs, changelog, more tests), that would get this moving. |
Note that this is not 'superfaces' syntax, it's regular markdown for Python: From the docs:
Superfences are about other things, like nesting and custom fences |
Description
When I'm writing docs, I frequently add code blocks like this:
Or like this:
I can see that both of these code blocks are supported in your package, as defined in this line:
blacken-docs/src/blacken_docs/__init__.py
Line 16 in 3199508
However, I'd like to extend this functionality to include two other identifiers for the Pygment langs:
".py"
".python"
The reason why is because in the
pymdown-extensions
package, it has some functionality called Super Fences: SuperFences. Here, it enables you to define some code blocks which allow you to inject some special syntax to generate html code with additional classes, id's, titles, line nums, etc.Here's an example:
Or like this:
You'll notice, also, that in order to use the functionality from the PyMdown-Extensions package, we also need to use curly brackets
{
and}
.When I use the syntax like this, then my docs are not automatically 'blackened' thanks to your excellent package.
Can you please extend your package to handle this functionality also?
I would recommend adjusting this line:
blacken-docs/src/blacken_docs/__init__.py
Line 16 in 3199508
To be like this:
And also adjusting this line:
blacken-docs/src/blacken_docs/__init__.py
Line 19 in 3199508
To be like this:
I hope that helps?
Thanks 👍
The text was updated successfully, but these errors were encountered: