aboutsummaryrefslogtreecommitdiff
path: root/shell/hush_test/hush-parsing/quote1.right
diff options
context:
space:
mode:
authorDenys Vlasenko <vda.linux@googlemail.com>2016-09-29 17:17:04 +0200
committerDenys Vlasenko <vda.linux@googlemail.com>2016-09-29 17:17:04 +0200
commit73c3e074df4de03ba1bebce09c130c8950ea5fe4 (patch)
tree68b486c969165596a922184a0dcdd59c53438589 /shell/hush_test/hush-parsing/quote1.right
parent8286513838beaf9ccaab15bb5905248c3b7b8a69 (diff)
downloadbusybox-73c3e074df4de03ba1bebce09c130c8950ea5fe4.tar.gz
ash: [PARSER] Handle backslash newlines properly after dollar sign
Fixes var_unbackslash1.tests failure. Upstream commit: [PARSER] Handle backslash newlines properly after dollar sign On Tue, Aug 26, 2014 at 12:34:42PM +0000, Eric Blake wrote: > On 08/26/2014 06:15 AM, Oleg Bulatov wrote: > > While playing with sh generators I found that dash and bash have different > > interpretations for <slash><newline> sequence. > > > > $ dash -c 'EDIT=xxx; echo $EDIT\ > >> OR' > > xxxOR > > Buggy. > > > > $ dash -c 'echo "$\ > > (pwd)"' > > $(pwd) > > > > Is it undefined behaviour in POSIX? > > No, it's well-defined, and dash is buggy. ... I agree. This patch should resolve this problem and similar ones affecting blackslash newlines after we encounter a dollar sign. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
Diffstat (limited to 'shell/hush_test/hush-parsing/quote1.right')
0 files changed, 0 insertions, 0 deletions