Re: Backslash mysteriously disappears in command expansion when unescapi
From:
Chet Ramey
Subject:
Re: Backslash mysteriously disappears in command expansion when unescaping would reference an existing file
Date:
Wed, 22 May 2019 11:05:24 -0400
User-agent:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
On 5/22/19 9:33 AM, Robert Elz wrote:
> Date: Wed, 22 May 2019 08:43:00 -0400
> From: Greg Wooledge <wooledg@eeg.ccf.org>
> Message-ID: <20190522124300.GZ1434@eeg.ccf.org>
>
> | It seems to be unique to bash 5. If it's a bug fix, then I'm not
> | understanding the rationale. Backslashes shouldn't be consumed during
> | glob expansion.
>
> They should - when a pattern comes from an expansion (be that a
> variable expansion, or as here, a command substitution) there needs
> to be a way to indicate whether the potential magic chars are in
> fact intended as magic chars, or as literals. \ is used for that.
There is more discussion in
http://lists.gnu.org/archive/html/bug-bash/2019-02/msg00151.html
--
``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/