We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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-ext
The GNU test case color-ext was failing because our ls command doesn't handle suffix letter cases.
touch img1.jpg IMG2.JPG img3.JpG file1.z file2.Z LS_COLORS="*.jpg=01;35:*.JPG=01;35;46" ls -U1 --color=always img1.jpg IMG2.JPG img3.JpG
our ls would produce output
^[0m^[01;35;46mimg1.jpg^[0m ^[01;35;46mIMG2.JPG^[0m ^[01;35;46mimg3.JpG^[0m
but it should be
^[0m^[01;35mimg1.jpg^[0m ^[01;35;46mIMG2.JPG^[0m img3.JpG
like wise
LS_COLORS="*.jpg=01;35;46:*.jpg=01;35:*.JPG=01;35;46" ls -U1 --color=always img1.jpg IMG2.JPG img3.JpG
our ls would give
In both cases, this is happening because lscolors doesn't care about the case sensitivity of the entries in the env.
lscolors
The text was updated successfully, but these errors were encountered:
ls command doesn't handle suffix letter cases
what do you mean by this ? :)
Sorry, something went wrong.
sorry, I was typing it and accidentally pressed Ctrl+enter
I already made an issue in lscolors's repo and working on a fix
Successfully merging a pull request may close this issue.
The GNU test case
color-ext
was failing because our ls command doesn't handle suffix letter cases.example 1
touch img1.jpg IMG2.JPG img3.JpG file1.z file2.Z LS_COLORS="*.jpg=01;35:*.JPG=01;35;46" ls -U1 --color=always img1.jpg IMG2.JPG img3.JpG
our ls would produce output
but it should be
like wise
example 2
LS_COLORS="*.jpg=01;35;46:*.jpg=01;35:*.JPG=01;35;46" ls -U1 --color=always img1.jpg IMG2.JPG img3.JpG
our ls would give
but it should be
In both cases, this is happening because
lscolors
doesn't care about the case sensitivity of the entries in the env.The text was updated successfully, but these errors were encountered: