Open bartico6 opened 1 week ago
As far as I remember, this has been the standard behaviour of the extension ever since it started supporting Markdown. The reason is simple: the extension was built to insert the "coded" notation of an Emoji. Since HTML is valid within Markdown, it escapes emojis the same way.
Personally, I don't see the need to use a VSCode extension to insert plain emojis – every modern operating system has an emoji picker. But that's just me. Everybody else can choose between many other extensions that do just that, both for plain emojis and the GfM notation.
I agree with your point that a plain emoji is more readable in a Markdown document, but again: this is not what the extension has been built for. Sorry to disappoint!
Ah, previously Markdown must've been unsupported because it inserted the emoji verbatim, and I guess I preferred that. After some update sometime ago it changed. Is there no straightforward way to return to that behaviour?
Unrelated but snippets were significantly more pleasant to use than the palette we have now, too - I was so used to just typing something like ji:checkmark
and tabbing the emoji into the document :sob:
Inputting emojis into Markdown now adds what appears to be an escaped HTML entity, even though emojis inserted as-is still appear to be perfectly supported by VSCode (included a screenshot of a preview plugin side by side with source file), GitHub and other markdown viewers.
Emojis inserted as is are significantly more readable while editing the file without a preview plugin (see screenshot
#2
)If the change is not intended, please revert it. If it is intentional - could you please explain why?