Jeff Quast

I have used to strike-through on the suggestion of the terminal sequence, I will save for another issue. As for the need for "width" function, just about every downstream library...

Although I am open to changing wcswidth() to never return -1 and make a "best effort", it would deviate from the original 2007 implementation and POSIX specification, and this is...

I have created it in development branch but I will make a bugfix release first, I will make a PR for this next, https://github.com/jquast/wcwidth/blob/1f1443b7af38b9e1b36a895b5d998f511021d377/wcwidth/wcwidth.py#L262-L277

I have revised this description and related issue #92 And I do think they are closely related. control characters like `\b` is just as much a *terminal sequences* as `\x1b[0m`....

Looks OK to me... @GalaxySnail ?

Thank you both all the attention and efforts and concerns. I understand that python 2 compatibility is difficult, especially for typing. I have created Issue #102 with my thoughts about...

Issue #79 proposes new width() function

See also #93 to just offer a proper rjust/etc. as part of the API

I just want to also add that this cannot be fixed in the wcwidth() and wcswidth() functions, as they intend to exactly match function signature and behavior of the POSIX...

Well, blessed is thread safe, I have successfully used it in a threaded terminal server project serving each client ip it’s own output (telnet 1984.ws a public server), It hasn’t...