Skip to content

fix(theme): ignore builtin LS_COLORS indicators#1856

Open
ychampion wants to merge 1 commit into
eza-community:mainfrom
ychampion:fix-ls-colors-indicators
Open

fix(theme): ignore builtin LS_COLORS indicators#1856
ychampion wants to merge 1 commit into
eza-community:mainfrom
ychampion:fix-ls-colors-indicators

Conversation

@ychampion

Copy link
Copy Markdown
Description

Fixes #1682.

LS_COLORS builtin keys such as su, sg, ca, and tw are dircolors file-type/control indicators, not filename globs. When eza does not implement one of those indicators, it now ignores it instead of adding a matching filename pattern.

EZA_COLORS keeps the existing behavior for eza-only keys such as su.

How Has This Been Tested?
  • env -u EZA_COLORS -u EXA_COLORS LS_COLORS='su=31' cargo run --quiet -- --color=always -1 /tmp/eza-lscolors-regression | od -An -tx1c -> 73 75 0a
  • cargo test --lib theme::customs_test -- --nocapture
  • cargo test
  • cargo clippy --lib -- -D warnings
  • cargo fmt --all -- --check

Copilot AI review requested due to automatic review settings July 8, 2026 09:08

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

Builtin LS_COLORS keys describe file types and control codes. When eza does not implement one of those keys, it should not fall through to filename glob parsing.

Fixes: eza-community#1682
@ychampion
ychampion force-pushed the fix-ls-colors-indicators branch from 7d18e34 to 2a3ab55 Compare July 14, 2026 21:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: eza interprets unsupported LS_COLORS keys as globs

2 participants