blob: 1992c54dd4ea6ef209412996513758b868347bc0 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
|
host=@host@
# `tests` is after `src`, so the target SciTECO is already
# built.
# Using the $BOOTSTRAP_SCITECO wouldn't make sense
# anyway as we don't want to test some preinstalled SciTECO.
SCITECO="@abs_top_builddir@/src/sciteco"
if [ $at_arg_valgrind != false ]; then
SCITECO="valgrind --tool=memcheck --leak-check=full --error-exitcode=66 $SCITECO"
fi
# For testing command-line editing:
SCITECO_CMDLINE="$SCITECO --no-profile --fake-cmdline"
# Control characters for testing immediate editing commands with $SCITECO_CMDLINE.
# Often, we can use {...} for testing rubout, but sometimes this is not enough.
# Directly embedding escapes into strings is not portable.
# Theoretically, we could directly embed control codes, but for the time being
# I am trying to keep non-TECO sources clean of non-printable characters.
RUBOUT=`printf '\8'`
RUBOUT_WORD=`printf '\27'`
ESCAPE=`printf '\33'`
# Make sure that the standard library from the source package
# is used.
SCITECOPATH="@abs_top_srcdir@/lib"
TECO_INTEGER=@TECO_INTEGER@
MAXINT32=2147483647
MININT32=-2147483648
MAXINT64=9223372036854775807
MININT64=-9223372036854775808
GREP="@GREP@"
# Glib debug options
G_SLICE=debug-blocks
G_ENABLE_DIAGNOSTIC=1
# For the Unicode tests - makes sure that UTF-8 characters
# are accepted on command lines.
case $host in
*-*-darwin*)
LC_ALL=`defaults read -g AppleLocale | @SED@ 's/@.*$//g'`.UTF-8
;;
*)
LC_ALL=C.UTF-8
;;
esac
# Default stack size on Linux (8M).
# Some platforms allow very large stack sizes, making it hard to test
# against potential stack overflows.
ulimit -s 8192
# Test strings used by multiple test cases
WORDS_EXAMPLE="navigating (words is useful"
|
