jerch

> The only thing I'd add, is that it might be useful to follow the pattern of some of the other string-based queries that have a parameter to choose between...

Some more thinking about such a mode extension: Apps operating on the normal scroll buffer prolly dont care about individual runwidths, maybe this new mode could be set as default...

> That seems sensible to me. You're already getting ragged-right when using emojis and ideographic languages, so this isn't much different is it? I don't know about the technical side...

> My stance is that wcwidth should be deprecated (recommended not to be used) and wcswidth be used instead (assuming that wcswidth is aware of grapheme clusters and VS15/VS16 as...

> @j4james ooh right. I forgot about margins. Sorry. I think we should at least try to find/define a default behavior for the margin issues, that terminals should follow. Maybe...

Wow, that draft is pretty on point and I am impressed, that you got it sorted that short. And I like it for being that short and concise. :+1: >...

I wonder, if regional indicator (RI, country flags) should also be standardized by this? When I was initially dealing with grapheme rules, I found them to be more tricky, but...

@christianparpart Hmm yeah, the rules prolly cover RI just fine. Well it was more an issue on my end, how I ended up building the carry for cluster additions during...

Well you have basically two (and a half) options here: - implement fully ISO-2022 compliance This is how terminals were meant to treat 7/8-bit data streams. Doing this gives you...

@christianparpart Also interested in your solution here (prolly would use a variation as a wasm build) :smile_cat: Regarding UTF8: For ASCII-only data (like DCS stuff, even better if you could...