Timeline for Markdown code snippets don't allow trailing spaces
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 16, 2018 at 13:47 | comment | added | Martijn Pieters | Even worse, this post isn't even about comments. :-P | |
| Feb 16, 2018 at 13:45 | comment | added | Martijn Pieters | And you are right, I misread your answer here. I thought the spaces caused the backticks to be ignored, mea culpa. | |
| Feb 16, 2018 at 13:44 | comment | added | Martijn Pieters | Right, but in this case the space caused issues and the backticks did not get parsed correctly. Perhaps I missed something there. | |
| Feb 16, 2018 at 13:31 | comment | added | balpha StaffMod | @MartijnPieters Quite the opposite. This answer explains how this behavior matches original Markdown and why it behaves that way. And your quote even says that the space is part of the delimiter -- and so it shouldn't be rendered. | |
| May 29, 2012 at 5:09 | comment | added | Andres Riofrio | See this question for a use case of trailing spaces. | |
| Feb 27, 2012 at 7:40 | comment | added | Tim Stone |
Hmm, the fact that the original implementation uses [ \t]* seems inconsistent with the syntax guide's statement that "The backtick delimiters surrounding a code span may include spaces — one after the opening, one before the closing" (emphasis mine). Of course, even with the example in this question I still don't understand the use case that benefits from leaving extra spaces in, so the implementation makes more sense to me anyway.
|
|
| Feb 27, 2012 at 7:19 | history | answered | balphaStaffMod | CC BY-SA 3.0 |