From 3522966d9584ec16e2f469acd0fe8727857a9d25 Mon Sep 17 00:00:00 2001 From: Robin Haberkorn Date: Mon, 29 Jun 2026 00:15:46 +0200 Subject: implemented the ^~ pattern match construct: the rest of the pattern will be an Advanced Regular Expression * Allows searching by regular expressions. We will never support all ARE constructs in TECO patterns, so this is useful to have available. * Can only be typed upcaret. This leaves ^E~q available as an escape-regexp string building construct. * Once we replace the pattern2regexp converter with a custom terex lexer, we might want to restrict ^~ to the beginning of the pattern. Currently, however it can be anywhere, so you can mix TECO patterns with regular expressions. --- doc/sciteco.7.template | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) (limited to 'doc/sciteco.7.template') diff --git a/doc/sciteco.7.template b/doc/sciteco.7.template index 87e8574..41f3abf 100644 --- a/doc/sciteco.7.template +++ b/doc/sciteco.7.template @@ -2050,10 +2050,17 @@ the space and horizontal tab characters. Matches one in a list of patterns. Any pattern match construct may be used. The pattern alternatives must be separated by commas. +.TP +.SCITECO_TOPIC ^~ +.BI ^~ +The rest of the pattern is an Advanced Regular Expression (ARE) +as in Tcl - see +.BR re_syntax (3). +This can only be typed with an upcaret. .LP All non-pattern-match-characters match themselves. -Note however that currently, all pattern matching is performed -.BR case-insensitive . +Pattern matching is performed case-insensitive by default, +but this can be controlled with the \fB^X\fP command. . . .SH FILE NAMES AND DIRECTORIES -- cgit v1.2.3