Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

README: In comparison to tmux, Unicode support might be noteworthy #28

Open
jaseg opened this issue Jan 7, 2016 · 5 comments
Open

README: In comparison to tmux, Unicode support might be noteworthy #28

jaseg opened this issue Jan 7, 2016 · 5 comments

Comments

@jaseg
Copy link

jaseg commented Jan 7, 2016

Hi,

after a quick test run I came to notice that (for me) a serious advantage of pymux over tmux is that it seems to more properly support unicode.

tmux has serious problems with non-ascii characters in the command line or window titles. To me, this mostly seems to stem from a lack of awareness on the part of the developers. I had a dive into the code once intending to fix this in tmux, but I quickly got discouraged by the homebrewn UTF-8 implementation they're using everywhere (no trace of other encodings) and the inconsistent use of that (some parts handle UTF-8, some just don't).

On pymux, I could not find any problems entering fullwidth characters encoded as multibyte UTF-8 sequences into command line or window titles.

Best regards

@jonathanslenders
Copy link
Member

Hi @jaseg,

Thanks a lot! I added it to the readme.

If you think of any thing that can be done better, don't hesitate to create an issue. Personally, I also have enough ideas, so as long as the time allows me, pymux will keep improving.

@jquast
Copy link

jquast commented Jan 8, 2016

author of wcwidth here, such nice things to say about full-width support, glad to see it recognized :)

@jonathanslenders
Copy link
Member

Yeah, thank you for creating that, @jquast!
(I just added wcwidth to the readme as well.)

@jquast
Copy link

jquast commented Jun 8, 2020

I might also like to bring attention to https://github.com/jquast/ucs-detect/ -- with the latest version of the wcwidth library, we can now detect and select the most appropriate version of unicode by exporting an environment variable, UNICODE_VERSION as demonstrated by this ucs-detect utility.

I wrote about it more detail here, https://jeffquast.com/post/terminal_wcwidth_solution/ (i was about to e-mail you @jonathanslenders but I think commenting on this old issue will do just fine, lol -- best wishes!)

@jonathanslenders
Copy link
Member

Hi @jquast: thank you so much for working on that. I'm going to read the article!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants