Fixed explanation of why the unset SHELL test is uselessif /bin/sh is bash.
authorDavid Levine <levinedl@acm.org>
Mon, 23 Jul 2012 01:19:19 +0000 (20:19 -0500)
committerDavid Levine <levinedl@acm.org>
Mon, 23 Jul 2012 01:19:19 +0000 (20:19 -0500)
test/whatnow/test-ls

index 7a1b77a..31afee2 100755 (executable)
@@ -64,8 +64,8 @@ echo 'ls' | TERM=dumb whatnow -noedit -prompt '' 2> "$actualerr" | \
 check "$expectederr" "$actualerr" 'keep first'
 check "$expected" "$actual" 'keep first'
 
-# Check with SHELL unset.  system () on Linux (glibc) seems to
-# always use /bin/sh, so this test won't reveal anything with it.
+# Check with SHELL unset.  This won't reveal any problems if
+# /bin/sh sets SHELL, which bash does.
 unset SHELL
 
 echo 'ls' | TERM=dumb whatnow -noedit -prompt '' 2> "$actualerr" | \