-
-
Notifications
You must be signed in to change notification settings - Fork 446
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
Color for Non-Executable Files is now gray for me with version 0.17.0. Everything else seems to be the correct color. #404
Comments
We had changed hard coded values of colors for filenames and made it so that we take all the values from You can use A tool like sharkdp/vivid can help you to generate |
Thanks that's really helpful. Fixed my issue on the latest version (and changed the colors on 0.16.0 too).
Reason 2 suggests there is a change introduced in 0.17.0 that seems to use the terminal colors if LS_COLORS is unset. Both versions 0.16.0 and 0.17.0, I can confirm use the LS_COLORS variable after I set it through one of the links you sent. Version 0.16.0 seems to use the colors from the chart that is currently on the FAQ section if LS_COLORS is not set, version 0.17.0 seems to use the 16 bit terminal colors (notice how the greens are the same in the lsd output and the terminal syntax highlighting above). |
Oh, my bad. We had support for Also thanks for reminding about the readme, that needs update now. |
I have the same issue. What's the solution to get the exact same colors as in 0.16.0? |
@foxale The fastest solution is to use version 0.16.0. Other than that you would have to generate an |
A temporary fix: #365 (comment) |
lsd --version
:lsd 0.17.0
echo $TERM
:xterm-kitty
(I can confirm this issue exists with urxvt, and just using the tty terminal with ctr+alt+f2. I've tried to use other users and switching shells and it persists.)echo $LS_COLORS
: (Confirmed to be not set)Expected behavior
The color for Non-Executable Files should be yellow.
Actual behavior
The color for Non-Executable Files is now gray for me which is my terminal default text color. This started happening a few months ago. This only effects Non-Executable Files, and everything else seems normal. I have no clue what could be causing this.
The text was updated successfully, but these errors were encountered: