It seems that the backslash as an escape character is parsed before the escape markup is. So every one backslash that you want to display you have to double up.
Bumping; is this still an issue?
~Nohbody?
"For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled." - Richard FeynmanTotally forgot about this issue.
\\
\\
Ok, the first one is escaping out each backslash individually, while the second is putting both backslashes within one set of escape code. Both display properly on the first try, with two backslashes, but going back to edit the one with each backslash escaped out separately still results in the issue shown in that text file a few posts (and a year ago) back.
edited 17th Feb '16 5:38:55 PM by Nohbody
All your safe space are belong to Trump~Nohbody, since you're more familiar with what's going on with this, would you mind adding it to Query Bugs if you haven't already?
I haven't previously, but it's there now.
edited 18th Feb '16 9:10:14 AM by Nohbody
All your safe space are belong to TrumpCool, thanks. Locking.
Normally, when demonstrating a wiki function without activating it, one uses the escape codes [= =] around the function in question.
However, for the double backslash used to break up lines without a double-spaced line, it partially ignores the escape code when trying to use it to show how it works, resulting in one of the slashes vanishing. When you go to edit the post, the slashes disappear completely, leaving just the escape code with nothing inside.
Here's what I mean, done as an upload elsewhere so wiki code processing isn't an issue.
I don't know how to address the issue, or even know that it's not just me doing it wrong, but it is kind of annoying.
All your safe space are belong to Trump