On 10/13/23 12:36 AM, Grisha Levit wrote:
AFAICT, everything works fine if parse_matched_pair just stores \^A as
is (as long as dequote_string doesn't drop trailing ^A's). This seems
a lot easier than the alternative of teaching the subst.c functions to
handle \^A^A and \^A^? specially but mayb
Date:Thu, 12 Oct 2023 21:36:48 -0700
From:Grisha Levit
Message-ID:
| There are some issues with parser output when the input has an unquoted
| backslash followed by a raw ^A character:
The NetBSD shell (and probably other ash derived shells) used to
have issues
There are some issues with parser output when the input has an unquoted
backslash followed by a raw ^A character:
$ bash -c $'echo ${_+\\\1}' |& cat -v
bash: line 1: bad substitution: no closing `}' in ${_+\^A^A}
$ bash -c $'[[ \1 =~ (\\\1) ]]' |& cat -v
bash: line 1: [[: invalid regular expressi
