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

bug: can't see the dashes in permission #234

Closed
smartding opened this issue Sep 9, 2023 · 4 comments · Fixed by #237
Closed

bug: can't see the dashes in permission #234

smartding opened this issue Sep 9, 2023 · 4 comments · Fixed by #237
Labels
errors Something isn't working

Comments

@smartding
Copy link

I'm using eza v0.11.0 in Arch Linux.

When I run "eza -l", the dashes in the permission column are invisible, as shown in the figure below:
image

I can see the dashes when color is disabled.

As a comparison, exa doesn't have this issue, as shown in the figure below:
image

@smartding smartding added the errors Something isn't working label Sep 9, 2023
@ghost
Copy link

ghost commented Sep 9, 2023

The dash color (along with other punctuation) can be changed in the EXA_COLOR environment variable, e.g.
EXA_COLORS="xx=37" will make the punctuation white. Does that fix it for you?

@kevinquillen
Copy link

Had this same issue switching from exa.

Adding export EXA_COLORS="xx=37" to my zshrc fixed the issue.

@PThorpe92
Copy link
Member

@smartding

To see if #237 will close this issue, we are looking for some feedback from users. It adds "Bright" color options, and switching from Black to Dark Gray for the default punctuation color may solve this on some terminals. The difference doesn't look like much on mine in particular, but it very well may make it show up.

@cafkafk
Copy link
Member

cafkafk commented Sep 10, 2023

Closing in favor of #240

@cafkafk cafkafk closed this as completed Sep 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
errors Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants