From 25e24258978e1f341310cded67598fe9ccd4a652 Mon Sep 17 00:00:00 2001 From: David Levine Date: Sun, 22 Jul 2012 20:19:19 -0500 Subject: [PATCH] Fixed explanation of why the unset SHELL test is uselessif /bin/sh is bash. --- test/whatnow/test-ls | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/test/whatnow/test-ls b/test/whatnow/test-ls index 7a1b77a..31afee2 100755 --- a/test/whatnow/test-ls +++ b/test/whatnow/test-ls @@ -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" | \ -- 1.7.10.4