done.
Paul Stodghill wrote:
I just did a package update and suddenly started seeing a bunch of
errors
like the following,
(20) (error/warning) Error in `post-command-hook' (setting hook to nil):
(wrong-number-of-arguments #<subr window-minibuffer-p> 0)
I think that the following fixes the problem. Could someone look this over
and check it in?
Thanks.
--- edit-utils/lazy-lock.el.orig Thu Jul 6 17:08:22 2000
+++ edit-utils/lazy-lock.el Thu Jul 6 17:08:44 2000
@@ -454,7 +454,7 @@
;; Do the visible parts of the buffer(s), i.e., the window(s).
(if (or (not lazy-lock-walk-windows)
(and (eq lazy-lock-walk-windows t) (one-window-p t)))
- (or (window-minibuffer-p)
+ (or (window-minibuffer-p (selected-window))
(lazy-lock-maybe-fontify-window (selected-window)))
(walk-windows #'lazy-lock-maybe-fontify-window
'no-minibuf (eq lazy-lock-walk-windows 'all-frames)))))
@@ -472,7 +472,7 @@
;; from FSF Emacs, which doesn't (or didn't?) have built-in timers.
;; using sit-for is unfriendly and can cause weird interactions.
(when (and (not (memq this-command lazy-lock-ignore-commands))
- (not (window-minibuffer-p))
+ (not (window-minibuffer-p (selected-window)))
lazy-lock-stealth-time)
(if lazy-lock-timeout-id (disable-timeout lazy-lock-timeout-id))
(setq lazy-lock-timeout-id
--
Ben
In order to save my hands, I am cutting back on my mail. I also write
as succinctly as possible -- please don't be offended. If you send me
mail, you _will_ get a response, but please be patient, especially for
XEmacs-related mail. If you need an immediate response and it is not
apparent in your message, please say so. Thanks for your understanding.
See also
http://www.666.com/ben/chronic-pain/