[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: address@hidden: C++-mode: Syntax highlighting: wrong color for funct
From: |
Richard M. Stallman |
Subject: |
Re: address@hidden: C++-mode: Syntax highlighting: wrong color for function identifier depending on the kind of whitespace that follows] |
Date: |
Sun, 12 Feb 2006 23:40:14 -0500 |
Here's the change I was talking about. Would someone please adapt
this _now_ to the current sources, and install it? Then please rename
before-font-lock-after-change-function to
font-lock-extend-region-function, and rename
font-lock-run-before-after-change-hook to font-lock-extend-region?
Then please ack this message.
;;;;;; Changelog entry
2002-05-10 Alan Mackenzie <address@hidden>
The following set of changes allows a major mode dynamically to
specify the region to fontify after a buffer change. (fast-lock.el
doesn't need changing.)
* font-lock.el
New abnormal hook before-font-lock-after-change-function,
New function font-lock-run-before-after-change-hook.
Changed font-lock-after-change-function.
* jit-lock.el
Changed jit-lock-after-change
* lazy-lock.el
Changed lazy-lock-defer-line-after-change and
lazy-lock-defer-rest-after-change.
;;;;;; End of Changelog entry
;;;;;; Patch
diff -c -x ChangeLog -x Makefile -x README
/usr/src/packages/BUILD/emacs-21.1/lisp/font-lock.el NEW/font-lock.el
*** /usr/src/packages/BUILD/emacs-21.1/lisp/font-lock.el Wed Sep 5
13:36:29 2001
--- NEW/font-lock.el Fri May 10 19:24:25 2002
***************
*** 1260,1270 ****
'(face nil syntax-table nil font-lock-multiline
nil)
'(face nil font-lock-multiline nil)))))
;; Called when any modification is made to buffer text.
(defun font-lock-after-change-function (beg end old-len)
! (let ((inhibit-point-motion-hooks t))
(save-excursion
(save-match-data
;; Rescan between start of lines enclosing the region.
(font-lock-fontify-region
(progn (goto-char beg) (beginning-of-line) (point))
--- 1260,1309 ----
'(face nil syntax-table nil font-lock-multiline
nil)
'(face nil font-lock-multiline nil)))))
+ (defvar before-font-lock-after-change-function nil
+ "If set to a function, this can specify the region to fontify after a
change.
+
+ This variable is a buffer-local abnormal hook whose value, if set, should be a
+ single function. The function gets called from the active font-lock
+ after-change function, and is intended to allow a major mode to calculate for
+ itself the region to be fontified after a buffer change.
+
+ The function is given three parameters, the standard BEG, END and OLD-LEN from
+ after-change-functions. It should return either a cons of the beginning and
end
+ buffer-positions \(in that order\) of the region to fontify, or nil (in which
+ case the default region will be used).")
+ (make-variable-buffer-local 'before-font-lock-after-change-function)
+
+ (defun font-lock-run-before-after-change-hook (beg end old-len)
+ "Run the hook function, if any, in before-font-lock-after-change-function,
+ returning its value (a cons of beg and end), if it's valid, else nil.
+
+ BEG END and OLD-LEN are the three parameters supplied by
+ after-change-functions."
+ (cond ((null before-font-lock-after-change-function) nil)
+ ((not (functionp before-font-lock-after-change-function))
+ (message "before-font-lock-after-change-function's value is not a \
+ function in buffer %S"
+ (buffer-name))
+ nil)
+ (t (let ((region (funcall before-font-lock-after-change-function beg
end old-len)))
+ (cond ((null region) nil)
+ ((or (not (consp region))
+ (not (wholenump (car region))) (not (wholenump (cdr
region)))
+ (not (<= (car region) (cdr region))))
+ (message "before-font-lock-after-change-function returned
%S. \
+ This isn't a cons \(beg.end\), with beg and end numbers, and beg <= end")
+ nil)
+ (t region))))))
+
;; Called when any modification is made to buffer text.
(defun font-lock-after-change-function (beg end old-len)
! (let ((inhibit-point-motion-hooks t) region)
(save-excursion
(save-match-data
+ ;; Does the major mode have its own ideas about the region to fontify?
+ (setq region (font-lock-run-before-after-change-hook beg end old-len))
+ (if region (setq beg (car region) end (cdr region)))
;; Rescan between start of lines enclosing the region.
(font-lock-fontify-region
(progn (goto-char beg) (beginning-of-line) (point))
diff -c -x ChangeLog -x Makefile -x README
/usr/src/packages/BUILD/emacs-21.1/lisp/jit-lock.el NEW/jit-lock.el
*** /usr/src/packages/BUILD/emacs-21.1/lisp/jit-lock.el Mon Jul 16 12:22:58 2001
--- NEW/jit-lock.el Fri May 10 18:59:36 2002
***************
*** 426,431 ****
--- 426,434 ----
(when jit-lock-mode
(save-excursion
(with-buffer-prepared-for-jit-lock
+ ;; Does the major mode have its own ideas about the region to fontify?
+ (let ((region (font-lock-run-before-after-change-hook start end
old-len)))
+ (if region (setq start (car region) end (cdr region))))
;; It's important that the `fontified' property be set from the
;; beginning of the line, else font-lock will properly change the
;; text's face, but the display will have been done already and will
diff -c -x ChangeLog -x Makefile -x README
/usr/src/packages/BUILD/emacs-21.1/lisp/lazy-lock.el NEW/lazy-lock.el
*** /usr/src/packages/BUILD/emacs-21.1/lisp/lazy-lock.el Thu Aug 16
14:25:15 2001
--- NEW/lazy-lock.el Fri May 10 19:00:47 2002
***************
*** 771,776 ****
--- 771,779 ----
(save-buffer-state nil
(unless (memq (current-buffer) lazy-lock-buffers)
(push (current-buffer) lazy-lock-buffers))
+ ;; Does the major mode have its own ideas about what to fontify?
+ (let ((region (font-lock-run-before-after-change-hook beg end old-len)))
+ (if region (setq beg (car region) end (cdr region))))
(remove-text-properties (max (1- beg) (point-min))
(min (1+ end) (point-max))
'(lazy-lock nil))))
***************
*** 784,789 ****
--- 787,795 ----
(push (current-buffer) lazy-lock-buffers))
(save-restriction
(widen)
+ ;; Does the major mode have its own ideas about what to fontify?
+ (let ((region (font-lock-run-before-after-change-hook beg end old-len)))
+ (if region (setq beg (car region) end (cdr region))))
(remove-text-properties (max (1- beg) (point-min))
(point-max)
'(lazy-lock nil)))))
;;;;;; end of patch.
--
Alan Mackenzie (Munich, Germany)
- Re: address@hidden: C++-mode: Syntax highlighting: wrong color for function identifier depending on the kind of whitespace that follows], (continued)
- Re: address@hidden: C++-mode: Syntax highlighting: wrong color for function identifier depending on the kind of whitespace that follows], Stefan Monnier, 2006/02/16
- Re: address@hidden: C++-mode: Syntax highlighting: wrong color for function identifier depending on the kind of whitespace that follows], Stefan Monnier, 2006/02/15
- Re: address@hidden: C++-mode: Syntax highlighting: wrong color for function identifier depending on the kind of whitespace that follows], Alan Mackenzie, 2006/02/16
- Re: address@hidden: C++-mode: Syntax highlighting: wrong color for function identifier depending on the kind of whitespace that follows], Stefan Monnier, 2006/02/16
- Re: address@hidden: C++-mode: Syntax highlighting: wrong color for function identifier depending on the kind of whitespace that follows], martin rudalics, 2006/02/17
- Re: address@hidden: C++-mode: Syntax highlighting: wrong color for function identifier depending on the kind of whitespace that follows], Stefan Monnier, 2006/02/17
- Re: address@hidden: C++-mode: Syntax highlighting: wrong color for function identifier depending on the kind of whitespace that follows], martin rudalics, 2006/02/16
- Re: address@hidden: C++-mode: Syntax highlighting: wrong color for function identifier depending on the kind of whitespace that follows], martin rudalics, 2006/02/16
Re: address@hidden: C++-mode: Syntax highlighting: wrong color for function identifier depending on the kind of whitespace that follows],
Richard M. Stallman <=
Re: address@hidden: C++-mode: Syntax highlighting: wrong color for function identifier depending on the kind of whitespace that follows], Alan Mackenzie, 2006/02/15