Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: Robert Elz <kre@munnari.OZ.AU>
Newsgroups: gnu.bash.bug
Subject: Re: Backslash missing in brace expansion
Date: Sat, 07 Dec 2019 00:23:03 +0700
Lines: 19
Approved: bug-bash@gnu.org
Message-ID: <mailman.419.1575653093.1979.bug-bash@gnu.org>
References: <20191206055304.076d6115afa3a4f2a6a21c34@schrader-schulte.de> <20191205201157.cd481936f76d95bbdfabc73c@schrader-schulte.de> <662e2328-f331-c554-afcf-fd3819f6beab@case.edu> <3405.1575652983@jinx.noi.kre.to>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: usenet.stanford.edu 1575653093 25228 209.51.188.17 (6 Dec 2019 17:24:53 GMT)
X-Complaints-To: action@cs.stanford.edu
Cc: bug-bash@gnu.org, chet.ramey@case.edu
To: Martin Schulte <gnu@schrader-schulte.de>
Envelope-to: bug-bash@gnu.org
In-Reply-To: <20191206055304.076d6115afa3a4f2a6a21c34@schrader-schulte.de>
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [generic]
X-Received-From: 2001:3c8:9009:181::2
X-BeenThere: bug-bash@gnu.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-bash>
List-Post: <mailto:bug-bash@gnu.org>
List-Help: <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID: <3405.1575652983@jinx.noi.kre.to>
X-Mailman-Original-References: <20191206055304.076d6115afa3a4f2a6a21c34@schrader-schulte.de> <20191205201157.cd481936f76d95bbdfabc73c@schrader-schulte.de> <662e2328-f331-c554-afcf-fd3819f6beab@case.edu>
Xref: csiph.com gnu.bash.bug:15700

    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