@Linc said:
R_J Something about Markdown + Prettify must have a bug. Code blocks definitely aren't supposed to work like that, obviously.
I find that using ~~~ to start and end a code block causes most html passed to be filtered out, while indenting the code block with 4 spaces causes the block to be entity encoded and displayed properly.
While we're on the topic of weird Markdown behaviours, the Strike button adds ~'s around text but that evidently doesn't translate to striked text. (So the button is useless.)
While we're on the topic of weird Markdown behaviours, the Strike button adds ~'s around text but that evidently doesn't translate to striked text. (So the button is useless.)
while the button in buttonbar in 2.1.1 inserts del tags, which do work.
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.
Comments
@R_J Something about Markdown + Prettify must have a bug. Code blocks definitely aren't supposed to work like that, obviously.
@Linc: I was quite surprised to see the logo but maybe it could be used as some kind of nice signature - lets test
logo in the lower right corner?
TADAAAAA!
I find that using
~~~to start and end a code block causes most html passed to be filtered out, while indenting the code block with 4 spaces causes the block to be entity encoded and displayed properly.Search first
Check out the Documentation! We are always looking for new content and pull requests.
Click on insightful, awesome, and funny reactions to thank community volunteers for their valuable posts.
While we're on the topic of weird Markdown behaviours, the Strike button adds ~'s around text but that evidently doesn't translate to striked text. (So the button is useless.)
while the button in buttonbar in 2.1.1 inserts del tags, which do work.
I may not provide the completed solution you might desire, but I do try to provide honest suggestions to help you solve your issue.