[arch-general] Htop 2.0 fonts
Hi! Since the update to 2.0 the usage graphs use nonexisting fonts - both TTY and uxterm show the "empty box" unicode character instead of the fonts shown on htop 2.0 screenshots. I did not find any missing dependency for htop on my system. Do anyone else have this issue? Any ideas? Shall I install a new font for this? If so, which one? Thank you in advance. Regards, Garmine
Might be a locale issue as opposed to a font issue. That being said, works fine here. $ locale LANG=en_GB.UTF-8 LC_CTYPE="en_GB.UTF-8" LC_NUMERIC="en_GB.UTF-8" LC_TIME="en_GB.UTF-8" LC_COLLATE="en_GB.UTF-8" LC_MONETARY="en_GB.UTF-8" LC_MESSAGES="en_GB.UTF-8" LC_PAPER="en_GB.UTF-8" LC_NAME="en_GB.UTF-8" LC_ADDRESS="en_GB.UTF-8" LC_TELEPHONE="en_GB.UTF-8" LC_MEASUREMENT="en_GB.UTF-8" LC_IDENTIFICATION="en_GB.UTF-8" LC_ALL=
On Tue, 16 Feb 2016 18:40:30 +0100, Nicolas F. wrote:
Might be a locale issue as opposed to a font issue. That being said, works fine here.
Oops, I missed the OP's "empty box" information. The OP likely expects what we get using utf8, but even iso88591 shows a tree, it's just not using "├─", but instead it's using "`-". What's the output of echo $LANG ? [rocketmouse@archlinux ~]$ locale LANG=en_US.utf8 LC_CTYPE="en_US.utf8" LC_NUMERIC="en_US.utf8" LC_TIME="en_US.utf8" LC_COLLATE="en_US.utf8" LC_MONETARY="en_US.utf8" LC_MESSAGES="en_US.utf8" LC_PAPER="en_US.utf8" LC_NAME="en_US.utf8" LC_ADDRESS="en_US.utf8" LC_TELEPHONE="en_US.utf8" LC_MEASUREMENT="en_US.utf8" LC_IDENTIFICATION="en_US.utf8" LC_ALL= [rocketmouse@archlinux ~]$ locale -a C de_DE de_DE@euro de_DE.iso88591 de_DE.iso885915@euro de_DE.utf8 deutsch en_GB en_GB.iso88591 en_GB.utf8 en_US.utf8 german POSIX [rocketmouse@archlinux ~]$ htop [rocketmouse@archlinux ~]$ LANG=de_DE.iso88591 htop [rocketmouse@archlinux ~]$ LANG=de_DE.utf8 htop [rocketmouse@archlinux ~]$ LANG=C htop [rocketmouse@archlinux ~]$ LANG=en_GB.iso88591 htop [rocketmouse@archlinux ~]$ echo $LANG en_US.utf8 It's simlar for tree. [rocketmouse@archlinux ~]$ LANG=en_GB.iso88591 tree | head -n3 . |-- :: |-- 0603f7b059f8cfa52a3d1359def64c89b5f4a3ed_800.jpg [rocketmouse@archlinux ~]$ tree | head -n3 . ├── :: ├── 0603f7b059f8cfa52a3d1359def64c89b5f4a3ed_800.jpg Regards, Ralf
On Tue, 16 Feb 2016 18:33:57 +0100, Garmine 42 wrote:
Since the update to 2.0 the usage graphs use nonexisting fonts
What is the "usage graph"? Do you mean the "tree view"? If so try pushing F5.
Tue, 16 Feb 2016 18:48:22 +0100 Ralf Mardorf <silver.bullet@zoho.com>:
What is the "usage graph"? Do you mean the "tree view"? If so try pushing F5.
F2, -> (choose a meter in one of the columns), hit SPACE (F4 in htop 1.x) --byte
Garmine 42 <mikro001@gmail.com> on Tue, 2016/02/16 18:33:
Hi!
Since the update to 2.0 the usage graphs use nonexisting fonts - both TTY and uxterm show the "empty box" unicode character instead of the fonts shown on htop 2.0 screenshots.
I did not find any missing dependency for htop on my system.
Do anyone else have this issue?
Any ideas? Shall I install a new font for this? If so, which one?
Thank you in advance.
Make sure your locales support UTF-8 and select a terminal font that has braille character. Terminus (package terminus-font) works perfectly fine. -- main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH" "CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];) putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
On 16 February 2016 at 22:46, Christian Hesse <list@eworm.de> wrote:
Garmine 42 <mikro001@gmail.com> on Tue, 2016/02/16 18:33:
Hi!
Since the update to 2.0 the usage graphs use nonexisting fonts - both TTY and uxterm show the "empty box" unicode character instead of the fonts shown on htop 2.0 screenshots.
I did not find any missing dependency for htop on my system.
Do anyone else have this issue?
Any ideas? Shall I install a new font for this? If so, which one?
Thank you in advance.
Make sure your locales support UTF-8 and select a terminal font that has braille character. Terminus (package terminus-font) works perfectly fine. -- main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH" "CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];) putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
Hi! I meant the usage graphs - e.g. the CPU usage graph in the section above the processes. Box drawing characters work fine. Next time I will supply a screenshot too. It was indeed a font issue, the one I used did not contain the braille characters. Because the same problem existed on my gettys I thought it was an encoding issue or something else. Using terminus font at the moment (as suggested) and it works perfectly fine. Thank you very much for the help! :) Garmine
On 2016年02月17日 00時06分, Garmine 42 wrote:
It was indeed a font issue, the one I used did not contain the braille characters. Because the same problem existed on my gettys I thought it was an encoding issue or something else. Using terminus font at the moment (as suggested) and it works perfectly fine.
Well, I am glad I was not the only one affected by this. I wish there were at least an option to decide which characters get displayed.
I had the same issue in xterm. Changing fonts didn't fix it, but switching to urxvt (with the same font) did. It seems like there's something screwy with xterm's unicode support. On Mon, Mar 7, 2016 at 12:12 AM, Grady Martin <sunnycemetery@gmail.com> wrote:
On 2016年02月17日 00時06分, Garmine 42 wrote:
It was indeed a font issue, the one I used did not contain the braille characters. Because the same problem existed on my gettys I thought it was an encoding issue or something else. Using terminus font at the moment (as suggested) and it works perfectly fine.
Well, I am glad I was not the only one affected by this. I wish there were at least an option to decide which characters get displayed.
On 8 March 2016 at 03:49, Maxwell Anselm <silverhammermba@gmail.com> wrote:
I had the same issue in xterm. Changing fonts didn't fix it, but switching to urxvt (with the same font) did. It seems like there's something screwy with xterm's unicode support.
On Mon, Mar 7, 2016 at 12:12 AM, Grady Martin <sunnycemetery@gmail.com> wrote:
On 2016年02月17日 00時06分, Garmine 42 wrote:
It was indeed a font issue, the one I used did not contain the braille characters. Because the same problem existed on my gettys I thought it was an encoding issue or something else. Using terminus font at the moment (as suggested) and it works perfectly fine.
Well, I am glad I was not the only one affected by this. I wish there were at least an option to decide which characters get displayed.
You need to enable unicode in xterm - i.e. use uxterm instead of xterm.
On Tue, Mar 8, 2016 at 3:57 AM, Garmine 42 <mikro001@gmail.com> wrote:
On 8 March 2016 at 03:49, Maxwell Anselm <silverhammermba@gmail.com> wrote:
I had the same issue in xterm. Changing fonts didn't fix it, but switching to urxvt (with the same font) did. It seems like there's something screwy with xterm's unicode support.
On Mon, Mar 7, 2016 at 12:12 AM, Grady Martin <sunnycemetery@gmail.com> wrote:
On 2016年02月17日 00時06分, Garmine 42 wrote:
It was indeed a font issue, the one I used did not contain the braille characters. Because the same problem existed on my gettys I thought it was an encoding issue or something else. Using terminus font at the moment (as suggested) and it works perfectly fine.
Well, I am glad I was not the only one affected by this. I wish there were at least an option to decide which characters get displayed.
You need to enable unicode in xterm - i.e. use uxterm instead of xterm.
I already have unicode enabled in xterm. And Braille does show up if I switch to the default bitmap font, but for whatever reason it doesn't show up when I use Dejavu Sans Mono (which I prefer). urxvt has no such problem.
On 2016年03月09日 16時31分, Maxwell Anselm wrote:
On Tue, Mar 8, 2016 at 3:57 AM, Garmine 42 <mikro001@gmail.com> wrote:
You need to enable unicode in xterm - i.e. use uxterm instead of xterm.
I already have unicode enabled in xterm. And Braille does show up if I switch to the default bitmap font, but for whatever reason it doesn't show up when I use Dejavu Sans Mono (which I prefer). urxvt has no such problem.
That is because DejaVu Sans Mono has no Braille glyphs, and xterm does not use fallback fonts. The Braille glyphs you see in urxvt are from another font. As a workaround for xterm, you can copy Braille glyphs into DejaVu Sans Mono. FontForge can help you do this. Xterm is able to display larger glyphs in the same amount of space as a urxvt fallback font, because urxvt fallback fonts adhere to the proportions of the primary font.
participants (8)
-
Christian Hesse
-
Garmine 42
-
goa
-
Grady Martin
-
Jens Adam
-
Maxwell Anselm
-
Nicolas F.
-
Ralf Mardorf