Re: Backslash missing in brace expansion

From	Robert Elz <kre@munnari.OZ.AU>
Newsgroups	gnu.bash.bug
Subject	Re: Backslash missing in brace expansion
Date	2019-12-07 00:23 +0700
Message-ID	<mailman.419.1575653093.1979.bug-bash@gnu.org> (permalink)
References	<20191206055304.076d6115afa3a4f2a6a21c34@schrader-schulte.de> <20191205201157.cd481936f76d95bbdfabc73c@schrader-schulte.de> <662e2328-f331-c554-afcf-fd3819f6beab@case.edu> <3405.1575652983@jinx.noi.kre.to>

Show all headers | View raw

    Date:        Fri, 6 Dec 2019 05:53:04 +0100
    From:        Martin Schulte <gnu@schrader-schulte.de>
    Message-ID:  <20191206055304.076d6115afa3a4f2a6a21c34@schrader-schulte.de>

  | Yes - sure. But then I'm wondering why the unquoted backtick doesn't
  | start command substitution:

Too late.   Syntax elements must be recognised by the parser, they cannot
(ever) appear from an expansion (if that's needed an "eval" is required).

I'm not sure I accept the explanation for the \ missing though, quoting is
also a parser activity (though some of it also happens in pattern matching).
But normally, backslashes (or any other form of quoting) that result from
expansions are simply characters.   Quote removal is only supposed to remove
quotes that were present on the original command line.

kre

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread

Thread

Re: Backslash missing in brace expansion Robert Elz <kre@munnari.OZ.AU> - 2019-12-07 00:23 +0700

csiph-web