Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #15700 > unrolled thread

Re: Backslash missing in brace expansion

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

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

#15700 — Re: Backslash missing in brace expansion

    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

[toc] | [standalone]

Back to top | Article view | gnu.bash.bug

csiph-web