diff options
| author | Pádraig Brady <P@draigBrady.com> | 2022-09-04 19:59:25 +0100 |
|---|---|---|
| committer | Pádraig Brady <P@draigBrady.com> | 2023-03-13 16:20:38 +0000 |
| commit | 47988fad885e8129f9dc36f0ed4d63375de23603 (patch) | |
| tree | 1eb1b78b48bb2472081c56c7a3a35208889d2e26 /NEWS | |
| parent | 1ac1d6def69e1faaefd1b41492764ef27c90b7a5 (diff) | |
| download | coreutils-47988fad885e8129f9dc36f0ed4d63375de23603.tar.gz | |
ls: --color: honor separate sequences for extension cases
Following on from commit v8.29-45-g24053fbd8 which unconditionally
used case insensitive extension matching, support selective
case sensitive matching when there are separate extension cases
defined with different display sequences.
* src/dircolors.hin: Document how file name suffixes are matched.
Note this is displayed with `dircolors --print-database` which
the texi info recommends to use for details.
* src/ls.c (parse_ls_color): Postprocess the list to
mark entries for case sensitive matching,
and also adjust so that unmatchable entries are more quickly ignored.
(get_color_indicator): Use exact matching rather than
case insensitive matching if so marked.
* tests/ls/color-ext.sh: Add test cases.
* NEWS: Mention the change in behavior.
Addresses https://bugs.gnu.org/33123
Diffstat (limited to 'NEWS')
| -rw-r--r-- | NEWS | 3 |
1 files changed, 3 insertions, 0 deletions
@@ -103,6 +103,9 @@ GNU coreutils NEWS -*- outline -*- reverting to the behavior in coreutils-9.0 and earlier. This behavior is now documented. + ls --color now matches a file extension case sensitively + if there are different sequences defined for separate cases. + printf unicode \uNNNN, \UNNNNNNNN syntax, now supports all valid unicode code points. Previously is was restricted to the C universal character subset, which restricted most points <= 0x9F. |