A fenced code block begins with a code fence, indented no more than three spaces.
What’s the use case for 1-3 spaces before the fence? I understand that four would indicate that the fence is itself actually part of an indented code block, and I get why fences can be longer than three ticks, but I can’t find a good reason to have spaces before the fence.
I mean, I get that you can slightly indent the code block using leading spaces that’ll be removed on render, but boy, that seems awkward, and I don’t know that I’ve ever wished I could do that. When would that be practical? Perhaps folks that enjoy two-space tabs and prefer fences?
If there’s no great “cultural” use case, don’t you have an Occam’s Parsing Razor argument (essentially, “to break a tie, don’t backtrack when parsing”) not to allow 1-3 spaces?
(Which is just to say I imagine there’s a cultural argument in here somewhere that I’m missing. ;^D)
No big deal either way; just curious about the use cases. Thanks!
A backtick string is a string of one or more backtick characters (`) that is neither preceded nor followed by a backtick.
Boy, that’s ungainly.
A backtick string is a string of one or more consecutive backtick characters (
`) which is followed and/or preceded by non-backtick characters."