On 10/12/23 7:11 PM, Grisha Levit wrote:
On Sat, Oct 7, 2023 at 9:57 AM Chet Ramey <chet.ra...@case.edu> wrote:
On 9/26/23 2:25 AM, Grisha Levit wrote:
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.
Sorry I guess this part was incomplete, based on your earlier comment in [1].
If we want to preserve the behavior of unquoted backslash causing a following
quoted character to become unquoted after quote_string_for_globbing:
$ B=\\ bash-5.2 -O failglob -c ': $B"*"'
bash-5.2: line 1: no match: \*
then unquoted_glob_pattern_p needs to recognize that circumstance.
Thanks for the update.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/