procyberian/emacs
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

(jit-lock-fontify-now): Don't bind

Browse source 
font-lock-beginning-of-syntax-function to nil.
This commit is contained in:
Gerd Moellmann 2001-01-19 16:19:07 +00:00
parent dc81f8a23b
commit 9724173bef
2 changed files with 14 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

5
lisp/ChangeLog
View file

@ -1,3 +1,8 @@
2001-01-19 Gerd Moellmann <gerd@gnu.org>
* jit-lock.el (jit-lock-fontify-now): Don't bind
font-lock-beginning-of-syntax-function to nil.
2001-01-19 Eli Zaretskii <eliz@is.elta.co.il>
* mail/emacsbug.el (report-emacs-bug): Report values of

11
lisp/jit-lock.el
View file

@ -264,8 +264,15 @@ Defaults to the whole buffer. END can be out of bounds."
(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