[GH-ISSUE #132] 256 Color output not working on urxvt #54

Closed
opened 2026-06-08 11:25:28 +03:00 by zhus · 7 comments
Owner

Originally created by @MithicSpirit on GitHub (Jan 17, 2021).
Original GitHub issue: https://github.com/bootandy/dust/issues/132

Despite using URxvt patched for 256color output, dust still uses the unicode "dither" characters in the usage boxes to the right. The 256color gradient works fine on Konsole for me. My $TERM environment variable is rxvt-unicode-256color and the output of tput color is 256.

Originally created by @MithicSpirit on GitHub (Jan 17, 2021). Original GitHub issue: https://github.com/bootandy/dust/issues/132 Despite using URxvt patched for 256color output, `dust` still uses the unicode "dither" characters in the usage boxes to the right. The 256color gradient works fine on Konsole for me. My `$TERM` environment variable is `rxvt-unicode-256color` and the output of `tput color` is `256`.
zhus closed this issue 2026-06-08 11:25:28 +03:00
Author
Owner

@bootandy commented on GitHub (Mar 2, 2021):

This is me:

$ echo $TERM xterm-256color

Do programs like dutree & exa work correctly with their colors?

<!-- gh-comment-id:789209876 --> @bootandy commented on GitHub (Mar 2, 2021): This is me: $ echo $TERM xterm-256color Do programs like dutree & exa work correctly with their colors?
Author
Owner

@MithicSpirit commented on GitHub (Mar 3, 2021):

No, those aren't working either. Though the script at https://gist.githubusercontent.com/HaleTom/89ffe32783f89f403bba96bd7bcd1263/raw/ does print the 256 color output correctly.

<!-- gh-comment-id:789282540 --> @MithicSpirit commented on GitHub (Mar 3, 2021): No, those aren't working either. Though the script at https://gist.githubusercontent.com/HaleTom/89ffe32783f89f403bba96bd7bcd1263/raw/ does print the 256 color output correctly.
Author
Owner

@bootandy commented on GitHub (May 12, 2021):

could be related to: https://github.com/bootandy/dust/issues/138

<!-- gh-comment-id:839555166 --> @bootandy commented on GitHub (May 12, 2021): could be related to: https://github.com/bootandy/dust/issues/138
Author
Owner

@bootandy commented on GitHub (Sep 4, 2021):

I'll look at this, the sample script provides shades of grey so it should be possible to detect if the terminal supports 256 color and support it.

<!-- gh-comment-id:912851243 --> @bootandy commented on GitHub (Sep 4, 2021): I'll look at this, the sample script provides shades of grey so it should be possible to detect if the terminal supports 256 color and support it.
Author
Owner

@cyhyraethz commented on GitHub (Dec 17, 2021):

I'm having the same problem with kitty terminal. $TERM is xterm-kitty, output of tput colors is 256, and the the bar graph comes out looking like this (the greys are solid and look good in gnome-terminal where $TERM is xterm-256color though):
Screenshot from 2021-12-17 02-19-06

<!-- gh-comment-id:996604134 --> @cyhyraethz commented on GitHub (Dec 17, 2021): I'm having the same problem with kitty terminal. `$TERM` is `xterm-kitty`, output of `tput colors` is `256`, and the the bar graph comes out looking like this (the greys are solid and look good in gnome-terminal where `$TERM` is `xterm-256color` though): ![Screenshot from 2021-12-17 02-19-06](https://user-images.githubusercontent.com/45051951/146529405-bb292ef7-06c4-4d5e-b9d8-93e71af9d857.png)
Author
Owner

@MithicSpirit commented on GitHub (Jan 6, 2022):

I have switched to Alacritty some time ago and, for a while, this issue persisted, but with a recent commit it was fixed (f717710, see issue https://github.com/alacritty/alacritty/issues/5485). This seems to be mainly a problem with the terminal, so feel free to mark this issue as closed.

However, it may be possible to work around this problem on terminals that don't properly support the "dither" characters (the ones in the BLOCKS array in display.rs) by adding 256-color support (specifically, using the character along with color codes for different shades of gray). Whether or not terminals support these characters would probably have to be done manually by either hardcoding based on the TERM envvar and/or adding a CLI flag.

<!-- gh-comment-id:1006280438 --> @MithicSpirit commented on GitHub (Jan 6, 2022): I have switched to Alacritty some time ago and, for a while, this issue persisted, but with a recent commit it was fixed ([`f717710`](https://github.com/alacritty/alacritty/commit/f7177101eda589596ab08866892bd4629bd1ef44), see issue https://github.com/alacritty/alacritty/issues/5485). This seems to be mainly a problem with the terminal, so feel free to mark this issue as closed. However, it may be possible to work around this problem on terminals that don't properly support the "dither" characters (the ones in the `BLOCKS` array in `display.rs`) by adding 256-color support (specifically, using the `█` character along with color codes for different shades of gray). Whether or not terminals support these characters would probably have to be done manually by either hardcoding based on the `TERM` envvar and/or adding a CLI flag.
Author
Owner

@bootandy commented on GitHub (Aug 23, 2022):

Closing this as won't fix. However, if someone wants to make this work with fancier 256 color terminals I'd accept a PR

<!-- gh-comment-id:1223769217 --> @bootandy commented on GitHub (Aug 23, 2022): Closing this as won't fix. However, if someone wants to make this work with fancier 256 color terminals I'd accept a PR
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bootandy/archived-dust#54