Jeff Quast

thanks, sorry about the 2 year delay :(

Thanks for figuring this one out @micahcowan, I had the same problem, I will see if I can find some special \#define as you suggest

I've submitted PR #22 should fix dos33 for BSD (or Mac OSX) users while being compatible with linux, I tested both. If it is accepted I can check elsewhere, like...

I believe this is an issue of xterm.js not handling Variation Selector-16, described here https://github.com/microsoft/vscode/issues/118905#issuecomment-1836842947 It is not a surprise that you also see this issue outside of xterm.js, only...

I have since found a few python bug reports, patches, and proposals for wcwidth in the standard library, linked below with a small number of choice quotes. The last issue...

Thank you for your feedback @rivo I honestly appreciate it, >> Any character following ZWJ ([U+200D](https://codepoints.net/U+200D)) when in sequence by function [wcwidth.wcswidth()](https://wcwidth.readthedocs.io/en/latest/api.html#wcwidth.wcswidth). > > How do you determine when such...

Problem is due to using a retina display and lsix is using `\e[14t` to determine pixel size instead of TIOCGWINSZ. A temporary workaround Under Preferences->Advanced Preferences, change option "Show inline...

> It doesn't make sense to me that iTerm is returning "points" instead of pixels ever. I'm not sure it makes sense either, maybe we should file a bug report...

I enjoy this comment the most, > This is rather philosophical question: if we want tox to be smart or stupid. https://github.com/tox-dev/tox/issues/149#issuecomment-247789717 I want it to be smart, like @signalpillar...

I'm really happy for your feedback and attention on this issue @danschwarz, thank you for writing!! I am planning to write an article to bring awareness to the issue you...