summaryrefslogtreecommitdiff
path: root/lisp/jit-lock.el
diff options
context:
space:
mode:
authorGerd Moellmann <gerd@gnu.org>1999-08-21 19:27:28 +0000
committerGerd Moellmann <gerd@gnu.org>1999-08-21 19:27:28 +0000
commita4bda243d2c200d05a45754ddbb7db82b37e919c (patch)
tree875c1514919041caae4f786a9bb303b60bc50949 /lisp/jit-lock.el
parentd39c88504e3c6b7a76895c200c2f1cf09f78b5b0 (diff)
downloademacs-a4bda243d2c200d05a45754ddbb7db82b37e919c.tar.gz
(jit-lock-function): Use line-beginning-position.
Don't unwind-protect font-lock-fontify-region.
Diffstat (limited to 'lisp/jit-lock.el')
-rw-r--r--lisp/jit-lock.el12
1 files changed, 2 insertions, 10 deletions
diff --git a/lisp/jit-lock.el b/lisp/jit-lock.el
index ffc4b1be3bc..d2e94fd69e4 100644
--- a/lisp/jit-lock.el
+++ b/lisp/jit-lock.el
@@ -268,18 +268,10 @@ is active."
;; functions seem to expects this, if I believe
;; lazy-lock.
(goto-char start)
- (unless (bolp)
- (beginning-of-line)
- (setq start (point)))
+ (setq start (line-beginning-position))
;; Fontify the chunk, and mark it as fontified.
- (unwind-protect
- (font-lock-fontify-region start end nil))
-
- ;; Even if we got an error above, mark the region as
- ;; fontified. If we get an error now, we're
- ;; probably getting the same error the next time we
- ;; try, so it's moot to try again.
+ (font-lock-fontify-region start end nil)
(add-text-properties start next '(fontified t))
;; Find the start of the next chunk, if any.