mattdm
April 19, 2021, 11:41pm
1
So there’s this little internet chat expression: ¯\_(ツ)_/¯ – the classic “shruggy”.
Tragically, Discourse’s markdown sees the first \ as an escape, and we get
¯_(ツ)_/¯
A MISSING ARM .
Poor shruggy!
Now I know that I can mis-use `` as I did above, or throw in a couple of extra escapes
¯\\\_(ツ)_/¯ → ¯\_(ツ)_/¯
but people replying via email will not necessarily know to do this – and those getting the message via email will also not have the escapes rendered.
I’m sure there are many more important things, but … maybe there could be a special case? ¯_(ツ)_/¯
6 Likes
sam
April 20, 2021, 6:38am
3
Special cases get you into a nightmare situation long term. That said… you can set up watched words to replace the “broken” version with your desired full shruggy.
No need for a new feature, you have it already
5 Likes
mattdm
April 20, 2021, 8:34am
4
Can I do that on my hosted plan?
sam
April 20, 2021, 8:35am
5
Yeah it is a core feature in your admin panel
3 Likes
mattdm
April 21, 2021, 3:16pm
7
Hmm, so… I added it to the Replace list…
and it works with the Test button, but does not seem to with actual posts. Any idea? Important shruggy feature! - #3 by mattdm - Site Feedback - Fedora Discussion
david
April 21, 2021, 5:07pm
8
Looks like the watched words are applied after the escaping, so you’ll need to replace the ‘broken’ version with the correct version
(temporarily) set up here on Meta: ¯\_(ツ)_/¯
4 Likes
mattdm
April 21, 2021, 5:42pm
9
Ah, interesting. I guess there’s a bug there, since the test doesn’t show that.
3 Likes
