No, @meglio, what @zogstrip mean is that:
:/ as well as
:confused: both map to
Emoji’s start off as simple text-based combos like
You have to be an old dog like myself to remember the times when we used text-based emoji’s on Unix talk.
So, there are a large number of combinations starting with a colon that may map into an emoji, but shouldn’t if it is not separated by a space (for example, the
:/ above, when attached to
http, should obviously mean
http:// instead of an emoji). Without this space rule, the MarkDown processor has no way to tell if there should be an emoji or not.
So, my suggestion remain: automatically add a space in front (or both in front and after) the emoji, when chosen by the emoji picker.
Or, alternatively, modify the emoji processor to only recognize fully-spelt emoji names in non-space applications. For example:
:/ is only recognized with a space before, but
:confused: is always recognized wherever it is.