Hey 👋 ! I'm an engineer fromWarp.So awesome to see this landed just 3 days ago - I wasjust digging deep into a fish-relatedStarship prompt issue which ultimately led me to Emoji_Presentation with Unicode for the ☁️ glyph (and related glyphs), so this is a wild coincidence haha 🔥 (I openedfish-shell/fish-shell#10461 just yesterday!). We useunicode-width to help calculate widths within our terminal grid, so this will help a bunch (we gotta fix up our widths + rendering logic).

Confirmed that the changes above help get the correct width of 2 for\u{2601}\u{FE0F} which maps to ☁️ with Emoji_Presentation via variation selector (as opposed to the previous result of 1) 🙌 !

Was curious when we expect this change will be included as part of a release cc@Manishearth perhaps? We're currently on version0.1 which we can update to0.1.11 but I believe this change isn't in a release cut yet, which makes sense given recency. We can also temporarily point to a commit directly as well, though ideally we'd avoid that for production Warp 😅 - just wanted to get a sense of the usual release cadence/cycle here?

And thanks a ton for working on this@Jules-Bertholet ! 🎉

Published 0.1.12

I will warn you though: UAX 11 is not, and will never be, 100% accurate for monospace terminal size computation. "monospace" is not a concept that consistently makes sense across Unicode, and crates making strong assumptions about that should rethink their model.

Published 0.1.12

I will warn you though: UAX 11 is not, and will never be, 100% accurate for monospace terminal size computation. "monospace" is not a concept that consistently makes sense across Unicode, and crates making strong assumptions about that should rethink their model.

Awesome, thanks!

Ah gotcha - ack, thanks for the note! Yeah, we'll definitely have some fallback behavior that ensures it's not a fully broken experience in any case.