@Crissov: Well, delimiting inline mark-up is a rather nasty problem: You want it be easy to type and to look unobstructive, but at the same time it must be unambiguos, unlikely to lead to accidental conflicts with author’s text, and now even distinguish between an unlimited number of different inline fragments to process in a number of different ways …!
I see no “perfect” solution for this, either (I use
$ for my private purposes, and still I’m unhappy about it…):
Re-using the last backtick-fence’s label would probably really useful, but think about mixing say [ASCIImath][am] in-line mark-up together in a text with say syntax-highlighting a programming language, also used in in-line fragments (in this case: backtick-delimited code spans).
I would expect no rule or rhyme in which order these in-line fragments would follow each other, so the need to distinguish the “kind” of each in-line marked-up fragment individually will not go away easily.
Out of the top of my head I would consider the following, preliminary, maybe, something kind-of-like syntax:
Regular CommonMark backtick-delimited inline code: yadda yadda
`int x = y < z`yadda yadda.
Inline “code” (raw text) that needs to be specially treated, just in the way “tagged” code blocks ought to be: yadda yadda
´C`int x = y < z`yadda yadda.
Did you noticed my sacrilege here? The character in front of the code block’s label is U+00B4 ACUTE ACCENT from ISO 8859 or ISO 10646 (or Windows code page 1252, if you insist), but not from ISO 646 (aka ASCII)!
One could call it “forward-tick”, and it would be visually and logically a nice match with the “back-tick” U+0060 GRAVE ACCENT, in my opinion.
But your taste and opinion could vary—and so will probably your keyboard
But honestly, I see no convincing reason why all of CommonMark text should be restricted to the 7-bit ASCII character set for all time. Doesn’t
cmark right now happily gobble up UTF-8 already?
[EDIT: I just saw that this site’s Markdown processor actually takes the ACUTE ACCENT as the beginning of a code span, and places the backtick inside it, until the end of the code span is finally—correctly—detected at the second GRAVE ACCENT aka backtick. Does CommonMark allow this? Here we go with conformance and protablilty ;-)]
[EDIT 2: Nope,
cmark (my build at least) does what I hoped for and does it right, in my view: the fragment above is transformed by
cmake -t html frag.txt >frag.out to (and yes:
frag.txt was in UTF-8):
<P>yadda yadda ´C<CODE>int x = y < z</CODE> yadda yadda</P>
So I accuse this site’s Markdown processor! (But I would do it anyway because of this extremely annoying treatment of line-breaks
as “hard”! Seen that? There is no blank line in my input, dammit! Who could ever come up with a stupid behaviour like this???) ]