-
-
Notifications
You must be signed in to change notification settings - Fork 817
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 Presets #604
Comments
I'd rather not overload But I would be in favor of updating the incomplete, outdated and boring-looking default LS_COLORS value. Probably with something like what
(I'd rather not use 24-bit colors by default, because they are not supported by some terminal emulators) |
released in v8.2.0. |
Originally posted by @sharkdp in #469 (comment)
You could change
--color
to accept a color preset rather than always or never.--color=rich
could be the preset in the demo,--color=lite
could be the current default,--color=none
could be no color, and--color=default
could be theLS_COLORS
variable with a fallback to thelite
preset (ornone
if it doesn't pass the Windows-related checks). And it could read other presets from files, making sure to ignore carriage returns for compatibility purposes.The text was updated successfully, but these errors were encountered: