On 10/12/23 7:11 PM, Grisha Levit wrote:
On Sat, Oct 7, 2023 at 9:57 AM Chet Ramey 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 pa
Date:Thu, 12 Oct 2023 16:11:09 -0700
From:Grisha Levit
Message-ID:
| If we want to preserve the behavior of unquoted backslash
| causing a following
| quoted character to become unquoted after quote_string_for_globbing:
Please don't. Something explicity quo
On Sat, Oct 7, 2023 at 9:57 AM Chet Ramey 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 wa
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 c
