rivo
I prefer not to add these kind of exceptions.
I think given the package rewrite from last year, this PR is not relevant anymore.
I believe this PR also doesn't apply anymore after the rewrite last year.
This PR doesn't apply anymore at this point.
> @rivo: you declare that our "Specification" is "missing some things", I would appreciate any further things that you find wrong. I guess VS15 was the main one. I noticed...
> Shouldn't the width of ｷﾞ be 2? This is U+FF77 and U+FF9E. U+FF77 is a half-width character, thus width=1. Is U+FF9E a separate character? The Grapheme Cluster Spec says...
I appreciate your thoughtful response. > monospace constraints of a terminal Our goals may differ but in my Golang implementation, I don't think I mention terminals at all. Of course,...
Is this issue still relevant? I believe Unicode should work properly now. If there is no further comment soon, I will close this issue.
Yes, it does that. The nature of `tview` (or, rather, `tcell`, which `tview` uses) is that it uses the entire screen to draw content into it. That's very different from...
Let me phrase this differently: We **need** a solution that is backwards compatible. The left/right arrow keys are already used. The other questions I listed above also need to be...