When the enable emoji shortcuts setting is enabled emoticons like :) get turned into actual emoji (). However, this can’t be bypassed with a simple backslash before it (\:)). This is inconsistent with other things where escape works, and on Discord, you have a similar setting:
However it is not forced – if I want :-) raw I can just type a backslash before it, and I get what I want.
To bypass it you need to use something like a zero-width character in between, or wrap a letter in angle brackets in the middle since those don’t render, etc. i.e.
:<g>), :)
which causes a bad ux for users who want a bit more freedom with how they write emoji.
I made a post about this on the roblox dev-forum which uses discourse, and I agree, having to always use empty characters, or anything to NOT use an emoji is kind of annoying; Emojis usually make your post a bit more unprofessional, and sometimes you want a little :) but you don’t want a
I hope this gets changed, (“I guess it woudn’t update since it’s open-source and everything;”)
Actually I found this topic because I just stumbled into this inquiry myself (tried to escape a smiley but alas, it turned into an emoji AND swallowed my escape character … the audacity, ahah)
We have an existing bypass for this in backtick, e.g. :-) and :) … plus code blocks … not really sure we need even more methods to achieve the same goal?
My point was more of using emoji in actual conversation, and wouldn’t it just be a matter of not rendering the emoji, keeping it as an emoticon if there is a backslash before it ?
`` are for inline code, if you’re not having a programming discussion using code blocks doesn’t make sense. Even if it was it still doesn’t make sense as inline codes are generally used for highlighting a single line of code or for highlighting class/member names and such.
Questo bug presenta una simile svista di progettazione come “gli underscore possono interrompere i collegamenti automatici”, ma potrebbe essere un espediente specifico possibile. Darò un’occhiata a cosa si può fare.
Un utente nel mio forum si è lamentato di questo problema di formattazione, ho disabilitato l’autocompletamento delle emoji come soluzione per il nostro caso d’uso, ma poiché Discourse è stato aggiornato a markdown-it v13 un po’ di tempo fa, il problema sembra persistere, mentre l’escape con barra rovesciata ora funziona su https://markdown-it.github.io/
Potrebbe essere dovuto al fatto che ember.js si basa ancora sulla versione 12 di markdown, come indicato qui?
). However, this can’t be bypassed with a simple backslash before it (\:)). This is inconsistent with other things where escape works, and on Discord, you have a similar setting:
has parity with `thinking` and *thinking*
