From 9539f71675c40485e448efb3c4e06afc8d102f94 Mon Sep 17 00:00:00 2001 From: Sean Anderson Date: Sun, 28 Feb 2021 16:29:51 -0500 Subject: hush: Fix assignments being misinterpreted as commands If there were no variable substitutions in a command, then initial assignments would be misinterpreted as commands, instead of being skipped over. This is demonstrated by the following example: => foo=bar echo baz Unknown command 'foo=bar' - try 'help' Signed-off-by: Sean Anderson --- test/cmd/test_echo.c | 2 ++ 1 file changed, 2 insertions(+) (limited to 'test/cmd') diff --git a/test/cmd/test_echo.c b/test/cmd/test_echo.c index 9d60d7d1a0b..091e4f823c9 100644 --- a/test/cmd/test_echo.c +++ b/test/cmd/test_echo.c @@ -34,6 +34,8 @@ static struct test_data echo_data[] = { */ {"setenv jQx X; echo \"a)\" ${jQx} 'b)' '${jQx}' c) ${jQx}; setenv jQx", "a) X b) ${jQx} c) X"}, + /* Test shell variable assignments without substitutions */ + {"foo=bar echo baz", "baz"}, /* Test handling of shell variables. */ {"setenv jQx; for jQx in 1 2 3; do echo -n \"${jQx}, \"; done; echo;", "1, 2, 3, "}, -- cgit v1.2.3