summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLars Ingebrigtsen <larsi@gnus.org>2021-02-05 09:36:58 +0100
committerLars Ingebrigtsen <larsi@gnus.org>2021-02-05 09:36:58 +0100
commitff701ce2b261acce1dfcd1fe137268d87d5eab35 (patch)
tree40420e603867049e551da46dd83d8f5e582ab5e3
parent6bd9dbf9593799913bed2d32eb736f1f27007303 (diff)
downloademacs-ff701ce2b261acce1dfcd1fe137268d87d5eab35.tar.gz
Correct the lispref manual about flushing ppss info
* doc/lispref/syntax.texi (Syntax Properties): Correct the information about flushing the state by copying the text from the doc string (bug#46274).
-rw-r--r--doc/lispref/syntax.texi8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/lispref/syntax.texi b/doc/lispref/syntax.texi
index d27053a1799..4a316a1bddb 100644
--- a/doc/lispref/syntax.texi
+++ b/doc/lispref/syntax.texi
@@ -573,10 +573,10 @@ 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}. However, it should not call
-@code{syntax-ppss-flush-cache}; so, it is not allowed to call
-@code{syntax-ppss} on some position and later modify the buffer at an
-earlier position.
+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.
@strong{Caution:} When this variable is non-@code{nil}, Emacs removes
@code{syntax-table} text properties arbitrarily and relies on