From 99327974549c8f62a9414de48654f420d279dc6f Mon Sep 17 00:00:00 2001 From: Gerd Moellmann Date: Fri, 19 Jan 2001 13:29:05 +0000 Subject: [PATCH] (jit-lock-after-change): If font-lock-multiline is nil, don't check the `font-lock-multiline' text property. --- lisp/ChangeLog | 5 +++++ lisp/jit-lock.el | 3 ++- 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/lisp/ChangeLog b/lisp/ChangeLog index c33ceb0c7ea..0122867cd19 100644 --- a/lisp/ChangeLog +++ b/lisp/ChangeLog @@ -1,3 +1,8 @@ +2001-01-19 Gerd Moellmann + + * jit-lock.el (jit-lock-after-change): If font-lock-multiline + is nil, don't check the `font-lock-multiline' text property. + 2001-01-19 Michael Kifer * viper.el: Call initial-major-mode on startup. diff --git a/lisp/jit-lock.el b/lisp/jit-lock.el index 9cd9d2929ec..5fa93f0b94a 100644 --- a/lisp/jit-lock.el +++ b/lisp/jit-lock.el @@ -422,7 +422,8 @@ will take place when text is fontified stealthily." (with-buffer-prepared-for-jit-lock ;; If we're in text that matches a multi-line font-lock pattern, ;; make sure the whole text will be redisplayed. - (when (get-text-property start 'font-lock-multiline) + (when (and font-lock-multiline + (get-text-property start 'font-lock-multiline)) (setq start (or (previous-single-property-change start 'font-lock-multiline) (point-min)))) -- 2.39.5