[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Backslash missing in brace expansion
From: |
Robert Elz |
Subject: |
Re: Backslash missing in brace expansion |
Date: |
Sat, 07 Dec 2019 00:23:03 +0700 |
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
- Re: Unicode range and enumeration support., (continued)
- Re: Unicode range and enumeration support., Robert Elz, 2019/12/24
- Re: Unicode range and enumeration support., Greg Wooledge, 2019/12/23
- Re: Unicode range and enumeration support., L A Walsh, 2019/12/23
- Re: unquoted expansion not working (was Re: Not missing, but very hard to see), Robert Elz, 2019/12/14
- Re: unquoted expansion not working (was Re: Not missing, but very hard to see), L A Walsh, 2019/12/15
- Re: Not missing, but very hard to see (was Re: Backslash missing in brace expansion), Chet Ramey, 2019/12/13
Re: Backslash missing in brace expansion,
Robert Elz <=