summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2021-02-05 13:06:07 +0200
committerEli Zaretskii <eliz@gnu.org>2021-02-05 13:06:07 +0200
commitc71e08eba94fc821616ab8d48847ff7130974d61 (patch)
tree90be409fd263e24e5a6bbb5107ceabe7698009aa
parent43bf7f1b06f5ca21a3af166e803b632934e6674d (diff)
downloademacs-c71e08eba94fc821616ab8d48847ff7130974d61.tar.gz
Fix last change in syntax.texi
* doc/lispref/syntax.texi (Syntax Properties): Fix wording in last change. (Bug#46274)
-rw-r--r--doc/lispref/syntax.texi9
1 files changed, 5 insertions, 4 deletions
diff --git a/doc/lispref/syntax.texi b/doc/lispref/syntax.texi
index 58f07c9644d..9adffcc18d3 100644
--- a/doc/lispref/syntax.texi
+++ b/doc/lispref/syntax.texi
@@ -573,10 +573,11 @@ and by Font Lock mode during syntactic fontification (@pxref{Syntactic
Font Lock}). It is called with two arguments, @var{start} and
@var{end}, which are the starting and ending positions of the text on
which it should act. It is allowed to call @code{syntax-ppss} on any
-position before @var{end}, but if it calls @code{syntax-ppss} on some
-position and later modifies the buffer on some earlier position,
-then it is its responsibility to call @code{syntax-ppss-flush-cache}
-to flush the now obsolete info from the cache.
+position before @var{end}, but if a Lisp program calls
+@code{syntax-ppss} on some position and later modifies the buffer at
+some earlier position, then it is that program's responsibility to
+call @code{syntax-ppss-flush-cache} to flush the now obsolete info
+from the cache.
@strong{Caution:} When this variable is non-@code{nil}, Emacs removes
@code{syntax-table} text properties arbitrarily and relies on