Jeff Quast

Hello @Minabsapi, Try changing, ``` print(f"got {val}. ({val.code})") ``` to, ``` print(f"got {val!r}. ({val.code})") ``` that is, display repr(val) rather than str(val) -- as the `val` in this case is...

I would gladly accept a PR of the suggested design into next release, be sure to use rmam and smam terminal capabilities Thank you!

I think it’s a good idea, to allow to install and use without curses, or, even with curses, to depend on jinxed instead, /etc/termcap or whatever isn’t maintained anymore, all...

I'll just add that I initially started using blessed because I had a hardware terminal at the time, and used TERM=wyse325 or some such, for use in https://github.com/jquast/x84, there were...

Hello, I maintain the python wcwidth library, and I recently wrote a [specification](https://wcwidth.readthedocs.io/en/latest/specs.html) that is of interest to this specific issue. I also wrote an automatic testing tool to asses...

This is resolved in today's release, sorry for the long turnaround

This is closed by https://github.com/jquast/wcwidth/pull/91 - About `U+00AD` in particular, it is part of the `Cf` category, **and the entire category of 'Cf' is now classified as zero-width**, along with...

It's a bit ambiguous isn't it? From https://codepoints.net/U+00AD, > is a code point reserved in some coded character sets for the purpose of breaking words across lines by inserting visible...

Thanks for relaying @richfelke ‘s thoughts, I’m in full agreement with all of them, especially for -1 as this kind of character is meant to be managed by the terminal...

This is fixed in today's release. On empty string, wcwidth returns 0. Thanks!