Skip to content

bug: eza interprets unsupported LS_COLORS keys as globs #1682

@heftig

Description

@heftig

Eza interprets unsupported LS_COLORS keys (such as su) as globs instead of ignoring them entirely. This results in a file called su being miscolored.

The code explicitly notes these get ignored:

eza/src/theme/ui_styles.rs

Lines 527 to 529 in 31b9a56

// Codes we don’t do anything with:
// MULTIHARDLINK, DOOR, SETUID, SETGID, CAPABILITY,
// STICKY_OTHER_WRITABLE, OTHER_WRITABLE, STICKY, MISSING

But the codes should still need to be handled as special, otherwise the caller will create a pattern from them.

This probably needs more than a trivial change, as su in LS_COLORS needs to be ignored but su in EXA_COLORS still needs to be handled as special_user_file. set_ls is also used on EXA_COLORS.

eza v0.23.4

Metadata

Metadata

Assignees

No one assigned

    Labels

    errorsSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions