From 07b52f78680858683acb4e40b158f8926285cae4 Mon Sep 17 00:00:00 2001 From: Robin Haberkorn Date: Tue, 19 Nov 2024 14:33:30 +0300 Subject: implemented search mode flag (^X): allow case-sensitive searches (closes #17) * Usually you will only want -^X for enabling case sensitive searches and 0^X for case-insensitive searches (which is also the default). * An open question is what happens if the user sets -^X and then calls a macro. The search mode flag should probably be stacked away along with the search-string. This means we'd need a ^X special Q-Reg as well, so you can write [^X[_ 0^X S...$ ]_]^X. Alternatively, the search mode flag should be a property of the macro frame, along with the radix. --- tests/testsuite.at | 2 ++ 1 file changed, 2 insertions(+) (limited to 'tests') diff --git a/tests/testsuite.at b/tests/testsuite.at index 4bd4cfe..e7d50da 100644 --- a/tests/testsuite.at +++ b/tests/testsuite.at @@ -95,6 +95,8 @@ AT_SETUP([Searches]) # You also cannot search for a single ASCII 5 using Caret+E. # 2 additional ^Q are translated to a single ^Q and interpreted at the search-pattern layer. AT_CHECK([$SCITECO -e "@I/^Q\05/ J @:S/^Q^Q^Q\05/\"F(0/0)'"], 0, ignore, ignore) +# Canse-sensitive search +AT_CHECK([$SCITECO -e "@I/XXX/J -^X @:S/xxx/\"S(0/0)'"], 0, ignore, ignore) AT_CLEANUP AT_SETUP([Editing local registers in macro calls]) -- cgit v1.2.3