You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 8, 2020. It is now read-only.
Hi. Do you have any ideas as to what causes this display behaviour:
(normal glibc)
(musl libc)
It only happens with musl libc, but "tree 1.7.0" uses the same characters to display lines, and that works fine. Both are using the latest snapshot of ncurses, both on the same host, same terminal, same font.
The text was updated successfully, but these errors were encountered:
The one on top is using ncurses in Unicode mode, the second one is in ASCII mode. What's the value of the $LANG and $LC_ALL variables on each case? To get Unicode mode, htop has to be compiled with --enable-unicode, and the libc must support locales such as en_US.UTF-8.
Sorry for the delay in replying. I've just tested again using the latest upstream source of both musl libc & ncurses, and I still get this result. I am using --enable-unicode, and $LC_ALL is set to en_GB.UTF-8 in both cases. $LANG is unset.
Here is another program I compiled using the exact same terminal, libraries, variables, etc (the program is nbwmon):
That's the bit that's confusing me - all other programs that link to libncursesw.a work as expected. It's only htop that I've seen so far have this problem.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi. Do you have any ideas as to what causes this display behaviour:
(normal glibc)
(musl libc)
It only happens with musl libc, but "tree 1.7.0" uses the same characters to display lines, and that works fine. Both are using the latest snapshot of ncurses, both on the same host, same terminal, same font.
The text was updated successfully, but these errors were encountered: