From e5884ab2166ab5a03294baa54601b8785e6d9727 Mon Sep 17 00:00:00 2001 From: Robin Haberkorn Date: Fri, 6 Dec 2024 17:20:52 +0300 Subject: support the ::S anchored search (string comparison) command (and ::FD, ::FR, ::FS as well) * The colon modifier can now occur 2 times. Specifying `@` more than once or `:` more than twice is an error now. * Commands do not check for excess colon modifiers - almost every command would have to check it. Instead, a double colon will simply behave like a single colon on most commands. * All search commands inherit the anchored semantics, but it's not very useful in some combinations like -::S, ::N or ::FK. That's why the `::` variants are not documented everywhere. * The lexer.checkheader macro could be simplified and should also be faster now, speeding up startup. Eventually this macro can be made superfluous, e.g. by using 1:FB or 0,1^Q::S. --- doc/sciteco.7.template | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'doc') diff --git a/doc/sciteco.7.template b/doc/sciteco.7.template index 1777d54..8c049ee 100644 --- a/doc/sciteco.7.template +++ b/doc/sciteco.7.template @@ -1346,6 +1346,11 @@ boolean instead. For instance if \(lq1000C\(rq would fail, \(lq1000:C\(rq will return 0 instead. .LP +.SCITECO_TOPIC :: +Two colons (\fB::\fP) can sometimes further modify a command's behavior \(em +currently it is used by the \fB::S\fP search comparison command. +On all other commands it will behave like a single colon. +.LP .SCITECO_TOPIC @ at When put in front of a command with string arguments, the at (\fB@\fP) modifier always allows the string termination character -- cgit v1.2.3