aboutsummaryrefslogtreecommitdiffhomepage
path: root/tests
diff options
context:
space:
mode:
authorRobin Haberkorn <robin.haberkorn@googlemail.com>2025-02-24 04:04:47 +0300
committerRobin Haberkorn <robin.haberkorn@googlemail.com>2025-02-24 04:04:47 +0300
commit376da1ea68879229d43704ebe70874020d0e8fd6 (patch)
tree9439709306f26395949c173287220b78697448a4 /tests
parent00dd53661570996c637d0d4b28188427e04f22bc (diff)
downloadsciteco-376da1ea68879229d43704ebe70874020d0e8fd6.tar.gz
fixed rubbing out `?` (help) after editing a Q-Register
* Test case: @EQa// @?/EX/ -- Rubout should return you to the Q-Register view. * The test suite has been extended. Unfortunately we cannot currently directly check whether we're editing a Q-Register. But we add a magic number of characters to the Q-Register, that we can check afterwards.
Diffstat (limited to 'tests')
-rw-r--r--tests/testsuite.at6
1 files changed, 6 insertions, 0 deletions
diff --git a/tests/testsuite.at b/tests/testsuite.at
index 3f0b7e5..eb71689 100644
--- a/tests/testsuite.at
+++ b/tests/testsuite.at
@@ -301,6 +301,12 @@ AT_CHECK([$SCITECO_CMDLINE "@^Um{:@S/XXX/} :Mm\"S(0/0)' Mm\"S(0/0)'"], 0, ignore
AT_FAIL_IF([$GREP "^Error:" stderr])
AT_CLEANUP
+AT_SETUP([Rub out help command])
+# Should restore the Q-Register view. But we cannot test this directly.
+AT_CHECK([$SCITECO_CMDLINE "@EQa// 23<@I/x/> @?/EX/{-6D} Z-23\"N(0/0)'"], 0, ignore, stderr)
+AT_FAIL_IF([$GREP "^Error:" stderr])
+AT_CLEANUP
+
AT_BANNER([Known Bugs])
AT_SETUP([Number stack])