-
-
Notifications
You must be signed in to change notification settings - Fork 320
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
code block \w filename #703
Comments
Nothing stopping an implementation from adopting what you've suggested whilst remaining CommonMark compliant right now. At the moment the spec doesn't mandate any particular treatment of the info string (not even the currently popular usage to specify the language is part of the spec currently).
Probably to have this standardised, it would be a prerequisite to first standardise the already popular language specifier in the info string. |
hmm, b/c the info string is so limited to just a single line... then i can think of 3 possible formats
urlencodedstandarlize the info string to be something like a javascript: example: the holy jsonWith json you would get support for other typed values like numbers where you wish to hint about eg the file size. javascript: example: Maybe a bit verbose? either way... simple to encode/decode. mimetype parsing metadataThis leave me to the last and final solution (suggestion) an example: tings that could be nice to present if the markdown decoder could would be to find useful informations such as
github's permalink could be something of a inspiration: Lines 8 to 9 in 1983605
|
hi 👋
today i saw another documentation today elsewhere and found this:
I struck me that many quite often want to present a code example and giving it an example filename along with it.
We sometimes see things such as:
i just thought that it would be a good idea if there was a spec'ed way of giving it an example filename:
The text was updated successfully, but these errors were encountered: