From 539d8626cda36957adc480d7f63c3557ad169f70 Mon Sep 17 00:00:00 2001 From: Alan Mackenzie Date: Sun, 1 Oct 2017 10:01:33 +0000 Subject: [PATCH] Remove inadvertent changes to syntax.texi in last commit. * doc/lispref/syntax.texi (Position Parse): revert changes. --- doc/lispref/syntax.texi | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/doc/lispref/syntax.texi b/doc/lispref/syntax.texi index b37f2b22b82..e3ae53536f9 100644 --- a/doc/lispref/syntax.texi +++ b/doc/lispref/syntax.texi @@ -751,8 +751,7 @@ position. This function does that conveniently. @defun syntax-ppss &optional pos This function returns the parser state that the parser would reach at -position @var{pos} starting from the beginning of the visible portion -of the buffer. +position @var{pos} starting from the beginning of the buffer. @iftex See the next section for @end iftex @@ -763,11 +762,11 @@ for a description of the parser state. The return value is the same as if you call the low-level parsing function @code{parse-partial-sexp} to parse from the beginning of the -visible portion of the buffer to @var{pos} (@pxref{Low-Level -Parsing}). However, @code{syntax-ppss} uses caches to speed up the -computation. Due to this optimization, the second value (previous -complete subexpression) and sixth value (minimum parenthesis depth) in -the returned parser state are not meaningful. +buffer to @var{pos} (@pxref{Low-Level Parsing}). However, +@code{syntax-ppss} uses a cache to speed up the computation. Due to +this optimization, the second value (previous complete subexpression) +and sixth value (minimum parenthesis depth) in the returned parser +state are not meaningful. This function has a side effect: it adds a buffer-local entry to @code{before-change-functions} (@pxref{Change Hooks}) for