Bug overview description:
When you include \

inside a \`literal\` markup clause, it inserts a code clause rather than the literal characters `\[code]`

[b]What part(s) of the site page(s) are affected?[/b]
Probably anywhere where it's possible to use marked-up text, but definitely in the forums.

[b]What is the expected behavior?[/b]
\`\[code]\` is rendered as a literal string `\[code]`

[b]What actual behavior is given instead?[/b]
\`\[code]\` is rendered as 

`[code]`

(actually worse than that, I had to insert a closing tag to make sure the code clause didn't effect the remainder of this post)

Time of incident (if applicable).
2018-05-23T09:30+09:30

Can you reproduce the bug every time?
Yes

What steps did you take to replicate this bug?
Writing this post, for example :)

Other:
It's possible to write this safely by escaping the leading [, as in
`\\\

\` . I still consider this a bug because it doesn't seem like there is any case in which \[code] could sensibly activate within a \`literal\` quote clause.
Further, other formatting tags such as `[b]` never take effect within literal quote clauses -- they just produce the literal characters `[b]` -- , so it is inconsistent for `\[code]` to do so.

After doing some messing around with it it seems that two symbols do not interact on opposite sides of a \[code] block. Nog sure if it's a bug or not but I think that's how it works.

MyNameIsOver20charac said:
not code [code]code [b]more[/b] code

[/code]code not code

After doing some messing around with it it seems that two symbols do not interact on opposite sides of a \[code] block. Nog sure if it's a bug or not but I think that's how it works. [/quote]

\

\

Huh. They work if you DEscape but the code block breaks them.