Zero Width Joiner Sequences lower adoptability of gitmoji

This is not an issue or complaint. I'd just like to raise the question, while the new "Improve developer experience" entry is relatively new and the first of its kind: should this project reconsider using Emoji ZWJ Sequences in the standard?

I appreciate that years of discussion went into #214. I like the choice that was made there (especially the fact that its gender-neutral). I don't want to ruin that and I don't really have a good alternative to suggest. I just want to point out that my use case—which I admit may be a little edgy, I'll elaborate on it below—was fully supported by gitmoji until 3.8.0, and that feels like a bit of a regression to me.

Details

I use: macOS,
git on the command line
vim when composing commit messages with bodies
actual emoji instead of :code:, because
- it helps keep my subject lines short
- I like to see them everywhere I'm working, not just in a GUI or website

What ends up happening now with the new 🧑‍💻 is, ironically, somewhat detrimental to the experience of this one developer 😅

in local zsh input or git log, it comes out as <0001f9d1><200d>💻
in vim, it's 🧑<200d>💻
in nano, it's 💻 preceded by two blank spaces
in local zsh output, the output of git commit, bash, or zsh on another machine via ssh, it comes out correctly as 🧑‍💻

So as best as I can tell it's not an issue with my terminal app, or my shell, but rather with certain terminal emulators and cli applications.

carloscuesta / gitmoji

Zero Width Joiner Sequences lower adoptability of gitmoji #981