Skip to content
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 for ``` for artwork elements #239

Open
rohanmahy opened this issue Jul 7, 2024 · 1 comment
Open

support for ``` for artwork elements #239

rohanmahy opened this issue Jul 7, 2024 · 1 comment

Comments

@rohanmahy
Copy link

I seem to remember that both triple backtick and triple tilde were allowed to delimit an block in the vague indeterminate past. in kramdown-rfc 1.7.17 only triple tilde is supported.

Is this a change?

In any case, it would be nice to support both.

@cabo
Copy link
Owner

cabo commented Jul 7, 2024

``` is a code span delimiter in markdown. The codeblock delimiter (fenced codeblocks) is ~~~.
(Please see the source of this comment to see why ``` is a code span delimiter.)

Upstream kramdown implements that; I'm not aware of having implemented anything beyond that.
So no, I don't think kramdown-rfc lost some functionality.

Obviously,

```
foo
```

is a paragraph with a code span inside, which can almost act like a codeblock in certain cases.

The problem with turning ``` into another codeblock fence is that this can change the meaning of existing documents. The footprint of such a change is probably small, so it can be argued whether that is worse or the confusion with people who learned markdown from GFM is worse. So I'll leave this issue open, in search for a good argument to add the alternate GFM fenced codeblock syntax to kramdown-rfc, or even possibly a better solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants