diff options
| author | Lars Ingebrigtsen <larsi@gnus.org> | 2016-04-29 22:44:13 +0200 |
|---|---|---|
| committer | Lars Ingebrigtsen <larsi@gnus.org> | 2016-04-29 22:44:13 +0200 |
| commit | 8f3a6de5e240910845594e079b2734a1acc1c25c (patch) | |
| tree | d175ce37b18d1b314597a81cc22d74aeb149fab0 | |
| parent | 2c3ab9b6e39a3d600e7d82deacc24effaec051bb (diff) | |
Warning fix in jit-lock-mode
* lisp/jit-lock.el (jit-lock-mode): Don't issue a warning when
turning the mode on in an indirect buffer, if this somehow has
happened (bug#17738).
| -rw-r--r-- | lisp/jit-lock.el | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/lisp/jit-lock.el b/lisp/jit-lock.el index 810c220516..c49fa6ed6c 100644 --- a/lisp/jit-lock.el +++ b/lisp/jit-lock.el @@ -195,9 +195,11 @@ the variable `jit-lock-stealth-nice'. If you need to debug code run from jit-lock, see `jit-lock-debug-mode'." (setq jit-lock-mode arg) (cond - ((buffer-base-buffer) - ;; We're in an indirect buffer. This doesn't work because jit-lock relies - ;; on the `fontified' text-property which is shared with the base buffer. + ((and (buffer-base-buffer) + jit-lock-mode) + ;; We're in an indirect buffer, and we're turning the mode on. + ;; This doesn't work because jit-lock relies on the `fontified' + ;; text-property which is shared with the base buffer. (setq jit-lock-mode nil) (message "Not enabling jit-lock: it does not work in indirect buffer")) |