coreutils/tests/ls/recursive
Jim Meyering 112efa81f2 Replace all occurrences of `(exit N); exit' with
`(exit N); exit N'.  Otherwise, those many tests could exit with
improper exit status when exiting via e.g., a trapped interrupt.
Thanks to a report from Bob Proulx.
2004-06-23 15:07:00 +00:00

69 lines
1023 B
Bash
Executable File

#!/bin/sh
# 4.1.1 and 4.1.2 had a bug whereby some recursive listings
# didn't include a blank line between per-directory groups of files.
if test "$VERBOSE" = yes; then
set -x
ls --version
fi
. $srcdir/../envvar-check
pwd=`pwd`
tmp=recursive.$$
trap 'status=$?; cd $pwd; rm -rf $tmp && exit $status' 0
trap '(exit $?); exit' 1 2 13 15
framework_failure=0
mkdir $tmp || framework_failure=1
cd $tmp || framework_failure=1
mkdir x y a b c a/1 a/2 a/3 || framework_failure=1
touch f a/1/I a/1/II || framework_failure=1
if test $framework_failure = 1; then
echo "$0: failure in testing framework" 1>&2
(exit 1); exit 1
fi
fail=0
# This first example is from Andreas Schwab's bug report.
ls -R1 a b c > out || fail=1
cat <<EOF > exp
a:
1
2
3
a/1:
I
II
a/2:
a/3:
b:
c:
EOF
cmp out exp || fail=1
test $fail = 1 && diff out exp 2> /dev/null
rm -rf out exp
ls -R1 x y f > out || fail=1
cat <<EOF > exp
f
x:
y:
EOF
cmp out exp || fail=1
test $fail = 1 && diff out exp 2> /dev/null
(exit $fail); exit $fail