summaryrefslogtreecommitdiff
path: root/lispref
diff options
context:
space:
mode:
authorGerd Moellmann <gerd@gnu.org>1999-10-10 21:25:17 +0000
committerGerd Moellmann <gerd@gnu.org>1999-10-10 21:25:17 +0000
commit08417ca310ab645932d34054a96ee61b36af6fa5 (patch)
tree7911b515e6e58b764ed259b5783d286c2156a958 /lispref
parent61a2c0a66aa8ad3a02b61be2f2876fbfaff344f7 (diff)
downloademacs-08417ca310ab645932d34054a96ee61b36af6fa5.tar.gz
Add patch from rms around line 1870.
Diffstat (limited to 'lispref')
-rw-r--r--lispref/modes.texi5
1 files changed, 5 insertions, 0 deletions
diff --git a/lispref/modes.texi b/lispref/modes.texi
index b0bb00771f7..727851f59c7 100644
--- a/lispref/modes.texi
+++ b/lispref/modes.texi
@@ -1870,6 +1870,11 @@ beginning of the @code{face} property. If it is @code{append}, the face
If @var{laxmatch} is non-@code{nil}, it means there should be no error
if there is no subexpression numbered @var{subexp} in @var{matcher}.
+Obviously, fontification of the subexpression numbered @var{subexp} will
+not occur. However, fontification of other subexpressions (and other
+regexps) will continue. If @var{laxmatch} is @code{nil}, and the
+specified subexpression is missing, then an error is signalled which
+terminates search-based fontification.
Here are some examples of elements of this kind, and what they do: