Re: XEmacs 21.5 and dired-gets-current-buffer-wrong bug
Ar an cúigiú lá is fiche de mí Bealtaine, scríobh Mats Lidell:
(defun my-lazy-lock-pre-idle-fontify-windows ()
(let ((buf (current-buffer)))
(lazy-lock-pre-idle-fontify-windows)
(if (not (eq buf (current-buffer)))
(message "Wrong buffer back from lazy-lock-pre-idle-fontify-windows"))))
And my message-buffer is now filled with "Wrong buffer back from
lazy-lock-pre-idle-fontify-windows" lines. So the problem is within
lazy-lock?
Indeed, and some mode-specific fontification code and not the general
lazy-lock code, since the rest of us aren’t seeing the problem.
C-x 4 F lazy-lock-pre-idle-fontify-windows RET , then copy the function into
*scratch*, and put in a (message ) just after the "(while t " that says
which frame is being fontified and whether the current buffer is the initial
(current-buffer).
--
Aidan Kehoe, http://www.parhasard.net/