# HG changeset patch
# User Gerd Moellmann <gerd@gnu.org>
# Date 979921012 0
# Node ID 1798ff4517d3bf4ab269e4fe344e8c1410e0aefe
# Parent  96ba5877dbd883b84f3b1e75f35df11eea402f0b
(jit-lock-fontify-now): Don't bind
font-lock-beginning-of-syntax-function to nil.

diff -r 96ba5877dbd8 -r 1798ff4517d3 lisp/jit-lock.el
--- a/lisp/jit-lock.el	Fri Jan 19 16:15:51 2001 +0000
+++ b/lisp/jit-lock.el	Fri Jan 19 16:16:52 2001 +0000
@@ -264,8 +264,15 @@
        (widen)
        (unless start (setq start (point-min)))
        (setq end (if end (min end (point-max)) (point-max)))
-       (let ((font-lock-beginning-of-syntax-function nil)
-	     next)
+       ;; This did bind `font-lock-beginning-of-syntax-function' to
+       ;; nil at some point, for an unknown reason.  Don't do this; it
+       ;; can make highlighting slow due to expensive calls to
+       ;; `parse-partial-sexp' in function
+       ;; `font-lock-fontify-syntactically-region'.  Example: paging
+       ;; from the end of a buffer to its start, can do repeated
+       ;; `parse-partial-sexp' starting from `point-min', which can
+       ;; take a long time in a large buffer.
+       (let (next)
 	 (save-match-data
 	   ;; Fontify chunks beginning at START.  The end of a
 	   ;; chunk is either `end', or the start of a region