dircolors: --csh doesn't escape `!`
Maintainers usually reply within 1 day
@majidninja is already working on this.
Since Nov 15, 2026.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
GNU coreutils now escapes ! in dircolors' csh output, and an ignored test already pins the expected behaviour: run cargo test --features unix --test tests -- --ignored test_dircolors::test_csh_output_escapes_bang to see it fail. Find where the --csh/setenv LS_COLORS string is built in the dircolors implementation under src/uu/dircolors/ and escape ! (and check whether other csh-special characters like ^ and # are handled nearby) alongside the existing quoting. Done means the ignored test passes and the dircolors suite is green.
Written by the indexing model from the issue text.
Description
GNU coreutils master now escapes ! in dircolors --csh output, so csh doesn't perform history substitution when evaluating it.
$ printf '*.hey! 01;33\n' > db; dircolors -c db
setenv LS_COLORS '*.hey!=01;33:' # uutils (csh history substitution)
setenv LS_COLORS '*.hey\!=01;33:' # GNU
Test added in #16493: cargo test --features unix --test tests -- --ignored test_dircolors::test_csh_output_escapes_bang
- Dominant language
- Rust
- Stars
- 24.4k
- Forks
- 2.2k
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 434
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from uutils/coreutils
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
U - shred
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
chown -v: `+ID` spec echoed verbatim on a broken symlinkPossibly taken @sunsss123soldier claimed this 1 day ago. Opengood first issue oss-scanner U - chown
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
dircolors: directory operand exits 2 with a custom message, GNU prints 'read error: Is a directory' and exits 1Possibly taken @emirmrkaljevic claimed this 3 days ago. OpenU - dircolors
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
test_hostid.rs lacks test cases with frozen ip addr e.g. unshare -ru sh -c "hostname 127.0.0.1 && hostid"Possibly taken @costajohnt claimed this 3 days ago. OpenU - hostid
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
All issues in uutils/coreutils
Similar issues
-
ai_p2
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
ClickHouse/ClickHouse#132519 ·
Maintainers usually reply within 1 day
-
Pattern-clip compiler tests miss the clip cap, sort order, muted output and count/emit agreementOpenarea: engine type: test
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
YuriiMurha/grooviq#224 ·
Maintainers usually reply within 1 day
-
state:needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
zed-industries/zed#67109 · 1 comment ·
Maintainers usually reply within 1 day
-
bug priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
storytold/photocraft#15500 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day