aboutsummaryrefslogtreecommitdiff
path: root/jim_tcl.txt
diff options
context:
space:
mode:
authorSteve Bennett <steveb@workware.net.au>2022-06-27 17:53:42 +1000
committerSteve Bennett <steveb@workware.net.au>2022-07-25 22:45:33 +1000
commitd1c3e1dfd55a046013a2718bf492ab6607209b99 (patch)
tree611f311d29a6c691b5356416be5dc687611dabbb /jim_tcl.txt
parentd222f25e3583402b940b9b1c42cf8f69b6e81b0a (diff)
downloadjimtcl-d1c3e1dfd55a046013a2718bf492ab6607209b99.zip
jimtcl-d1c3e1dfd55a046013a2718bf492ab6607209b99.tar.gz
jimtcl-d1c3e1dfd55a046013a2718bf492ab6607209b99.tar.bz2
docs: minor asciidoc formatting fixes
Signed-off-by: Steve Bennett <steveb@workware.net.au>
Diffstat (limited to 'jim_tcl.txt')
-rw-r--r--jim_tcl.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/jim_tcl.txt b/jim_tcl.txt
index 572670c..f1ab2cd 100644
--- a/jim_tcl.txt
+++ b/jim_tcl.txt
@@ -1136,7 +1136,7 @@ and POSIX are highlighted below.
1. UTF-8 strings and patterns are both supported
2. All Tcl character classes are supported (e.g. +[:alnum:]+, +[:digit:]+, +[:space:]+), but...
3. Character classes apply to ASCII characters only
-4. Supported shorthand character classes: +{backslash}w+ = +[:alnum:]+, +{backslash}W+ = +^[:alnum:]+, +{backslash}d+ = +[:digit:],+ +{backslash}D+ = +^[:digit:],+ +{backslash}s+ = +[:space:]+, + +{backslash}S+ = +^[:space:]+
+4. Supported shorthand character classes: +{backslash}w+ = +[:alnum:]+, +{backslash}W+ = +\^[:alnum:]+, +{backslash}d+ = +[:digit:],+ +{backslash}D+ = +\^[:digit:],+ +{backslash}s+ = +[:space:]+, + +{backslash}S+ = +^[:space:]+
5. Supported constraint escapes: +{backslash}m+ = +{backslash}<+ = start of word, +{backslash}M+ = +{backslash}>+ = end of word, +{backslash}A+ = start of string, +{backslash}Z+ = end of string
6. Backslash escapes may be used within regular expressions, such as +{backslash}n+ = newline, +{backslash}uNNNN+ = unicode
7. Support for the +?+ non-greedy quantifier. e.g. +*?+
@@ -3785,10 +3785,10 @@ The following switches modify the behaviour of +'regexp'+
+*-line*+::
Use newline-sensitive matching. By default, newline
is a completely ordinary character with no special meaning in
- either REs or strings. With this flag, +[^+ bracket expressions
- and +.+ never match newline, an +^+ anchor matches the empty
+ either REs or strings. With this flag, +*[\^*+ bracket expressions
+ and +*.*+ never match newline, an +*^*+ anchor matches the empty
string after any newline in the string in addition to its normal
- function, and the +$+ anchor matches the empty string before any
+ function, and the +*$*+ anchor matches the empty string before any
newline in the string in addition to its normal function.
+*-indices*+::