@sil unless I'm mistaken, that would be against the unicode spec - 😍 is a full-width character so it should take two spaces, as are many asian characters (ex ឤ)
spec annex: https://www.unicode.org/reports/tr11/
this rust crate doc I've never used is helpful: https://docs.rs/unicode-width/latest/unicode_width/#rules-for-determining-width
(this is possibly me way not getting the joke, but I've been interested in calculating accurate unicode string width in a terminal)
@llimllib really? it's not meant to be possible at all??
OK, didn't know that. Also that's really annoying in my monospace text editor :)
@sil yeah, I think it's basically an encoding of how asian languages were supported pre-unicode-standard; some characters were "half-width" (which in the terminal means width 1) and others "full-width" (2 grid spaces)
@sil and basically every terminal emulator gets it wrong all the time!
@mitchellh wrote about it here, he had to implement a worse method to be compatible with other terminals: https://mitchellh.com/writing/grapheme-clusters-in-terminals
@mavit it is. I don't actually know a solution to this other than "make one font which has every character in it and they're all the same width", which is the thing I was vaguely hoping someone had already done :-)