Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15703 > unrolled thread
| Started by | Eric Blake <eblake@redhat.com> |
|---|---|
| First post | 2019-12-06 13:37 -0600 |
| Last post | 2019-12-06 13:37 -0600 |
| Articles | 1 — 1 participant |
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.
Re: Backslash missing in brace expansion Eric Blake <eblake@redhat.com> - 2019-12-06 13:37 -0600
| From | Eric Blake <eblake@redhat.com> |
|---|---|
| Date | 2019-12-06 13:37 -0600 |
| Subject | Re: Backslash missing in brace expansion |
| Message-ID | <mailman.430.1575661041.1979.bug-bash@gnu.org> |
On 12/6/19 11:27 AM, Chet Ramey wrote:
> On 12/6/19 9:23 AM, Robert Elz wrote:
>
>> 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.
>
> Quote removal is a word expansion, and removes quotes that were present in
> the original word passed to word expansion. Brace expansion is performed
> before any of the POSIX word expansions, and is logically a separate step.
Then that argues that {Z..a} should produce \\ and \', rather than bare
characters, so that the subsequent quote removal gets back to the
intended character.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
Back to top | Article view | gnu.bash.bug
csiph-web