Don’t use hardcoded color values

[ariasuni]

Images file names are illegible on my computer; but I can’t change their colors because it’s hardcoded. There’s a few of them:

https://github.com/ogham/exa/search?utf8=%E2%9C%93&q=Fixed&type=

Would you accept a pull request that change those fixed values? For example, the purple color used for music, Fixed(92), would become ansi_term::Colour::Purple.

[weilbith]

I''ve similar problems. I love this tool, but folders (which are quite common I guess), aren't well visible in my colour-scheme. I guess having these colors hard-coded is faster, but I would trade this millisecond for the possibility to adjust them.

@ariasuni do you have already an adjusted implementation in a fork I could use? #370 doesn't so, am I correct?

[ariasuni]

You can build my branch use-only-named-colors on my fork of the repository, since exa has only received a few commits and no release in the meantime. Any feedback is appreciated.

[rugk]

Also related to #425

[novoid]

I do have a similar issue with not being able to read executable items using exa v0.8.0 and a dark theme: https://ibb.co/SwGDTKD

[rugk]

Fixed by #607 (?)

[ariasuni]

It’s not fixed for file types.

Would you accept a PR taking the same approach than #607 for file types (and also punctuation), @ogham?

This would solve the issue for me, and we can still argue about the default colors later.

[ariasuni]

exa is unmaintained (see #1243), and there’s a theme configuration file in the active fork eza.

See: https://github.com/eza-community/eza/blob/main/man/eza_colors-explanation.5.md#theme-configuration-file