The age-old problem with ¯\_(ツ)_/¯ is that it sucks in Markdown. As a fellow ¯\_(ツ)_/¯ enjoyer, I would like to share that the first arm you type requires three of \ because a backslash tells Markdown to ignore the special properties of the next character. This is called “escaping” a character.
Underscores italicize the text they surround, so the first backslash is read as escaping underscore if you paste the ¯\_(ツ)_/¯ in its regular form. The 1st backslash escapes the 2nd. The 2nd is displayed normally since it is escaped. The third escapes the following underscore to prevent the italicization of (ツ) and consequently the missing of shoulders.
I hope this helps you enjoy ¯\_(ツ)_/¯ more in the future!
The age-old problem with ¯\_(ツ)_/¯ is that it sucks in Markdown. As a fellow ¯\_(ツ)_/¯ enjoyer, I would like to share that the first arm you type requires three of \ because a backslash tells Markdown to ignore the special properties of the next character. This is called “escaping” a character.
Underscores italicize the text they surround, so the first backslash is read as escaping underscore if you paste the ¯\_(ツ)_/¯ in its regular form. The 1st backslash escapes the 2nd. The 2nd is displayed normally since it is escaped. The third escapes the following underscore to prevent the italicization of (ツ) and consequently the missing of shoulders.
I hope this helps you enjoy ¯\_(ツ)_/¯ more in the future!