[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: PATCH] unquoted_glob_pattern_p: better recognition
From: |
Chet Ramey |
Subject: |
Re: PATCH] unquoted_glob_pattern_p: better recognition |
Date: |
Sat, 7 Oct 2023 12:57:56 -0400 |
User-agent: |
Mozilla Thunderbird |
On 9/26/23 2:25 AM, Grisha Levit wrote:
A `/' followed by `(' should not be considered an unquoted glob character:
$ bash -O failglob -c ': $1' _ 'a/(b)'
_: line 1: no match: a/(b)
If extglob is not turned on, it probably doesn't make sense to treat words
that don't have any non-extended glob characters as patterns:
$ bash -O failglob -c ': $1' _ '+(x)'
_: line 1: no match: +(x)
A CTLESC-escaped character should be treated as such even if it follows an
unquoted backslash, same as in quote_string_for_globbing:
Thanks for the report and patch.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
- Re: PATCH] unquoted_glob_pattern_p: better recognition,
Chet Ramey <=