-
-
Notifications
You must be signed in to change notification settings - Fork 321
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
Tildes and backticks in info strings. #119
Comments
Some thoughts on this: The only good reason for disallowing backticks in the info string is to allow the use of 3+ backticks for inline code, e.g.
Of course, the solution is only partial; backtick style fenced code blocks mean that you can't hard-wrap this kind of inline code span; the closing backticks must be on the same line as the opener. This is an argument against using backticks for fenced code blocks, but it's probably too well established in Markdown to change that. Anyway, this reason for disallowing backticks doesn't apply to tildes, so perhaps tildes should be allowed in the info string. A nice advantage of allowing them would be that you could write stuff like this:
which looks rather nice! |
See also #197. |
0.28 says:
This disallows
|
Ping. At the moment, the following results in a code block in commonmark.js (dingus link):
But according to the spec it's not allowed:
|
The spec says:
So:
~~~ ~~
and ```` ``` are not allowed as an opening code fence.aa
isn't allowed either.~~~ aa ~~~
allowed? stmd.js doesn't accept it, but it's not clear from the spec.~~~ ``` and ```` ~~
are allowed.The text was updated successfully, but these errors were encountered: