From c8d305d89f06e0d6612b7acdc91cb8775f5667b1 Mon Sep 17 00:00:00 2001 From: Denys Vlasenko Date: Fri, 6 Aug 2010 19:28:04 +0200 Subject: [PATCH] var_bash4.tests: better wording in comment Signed-off-by: Denys Vlasenko --- shell/ash_test/ash-vars/var_bash4.tests | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/shell/ash_test/ash-vars/var_bash4.tests b/shell/ash_test/ash-vars/var_bash4.tests index 01a0def51..a6e98fd86 100755 --- a/shell/ash_test/ash-vars/var_bash4.tests +++ b/shell/ash_test/ash-vars/var_bash4.tests @@ -1,12 +1,12 @@ # This testcase demonstrates that backslashes are treated differently # in 1st and 2nd parts of ${var/search/repl}: -# if quoted: "${var/search/repl}", and repl contains \a (a non-special char), -# the backslash in repl stays; if unquoted, backslash: removed +# if quoted ("${var/search/repl}"), and repl contains \a (a non-special char), +# the backslash in repl stays; if unquoted, backslash is removed. # But search part does not act like that: \a is always converted to just a, # even in quotes. # -# bash4 (and probably bash3 too) result: "Quoted:" results are different - -# they have extra backslash before z. +# bash4 (and probably bash3 too): "Quoted:" results are different from +# unquoted and assignment expansions - they have a backslash before z. v='a*b\*c' echo 'Source: ' "$v" -- 2.25.1