Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #16645
| From | Robert Elz <kre@munnari.OZ.AU> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Bug Report concerning backslash in bash5 |
| Date | 2020-07-29 15:39 +0700 |
| Message-ID | <mailman.240.1596011979.2739.bug-bash@gnu.org> (permalink) |
| References | <4099319f-bc5e-a2ef-cfe8-6189df5a44b6@archlinux.org> <87ft9azxwb.fsf@hobgoblin.ariadne.com> <25979.1596011941@jinx.noi.kre.to> |
Date: Tue, 28 Jul 2020 22:41:52 -0400
From: Eli Schwartz <eschwartz@archlinux.org>
Message-ID: <4099319f-bc5e-a2ef-cfe8-6189df5a44b6@archlinux.org>
| I'm not sure what point you're trying to make here. Are you arguing that
| *printing* these backslash escapes is valid behavior here, and the
| reporter has merely misunderstood the shell rules?
Neither I suspect, Dale just didn't notice which backslashes Ralph
meant were the problem - the one in the expansion of $BLA was never
it, it is the others that appeared - which is an obvious bug
(probably something trivial) which I would expect will be quickly fixed.
kre
Back to gnu.bash.bug | Previous | Next | Find similar
Re: Bug Report concerning backslash in bash5 Robert Elz <kre@munnari.OZ.AU> - 2020-07-29 15:39 +0700
csiph-web