bogus interaction between blink-cursor-mode and the debugger

Hello all, I finally got around to figuring out why I keep getting an error whenever I invoke the xemacs debugger. To demonstrate the behavior, evaluate the following in the scratch buffer of a fresh xemacs (-q): (progn (blink-cursor-mode) (defun frobnicate ()) (debug-on-entry 'frobnicate) (frobnicate)) After a brief pause, the error message `Wrong type argument: number-char-or-marker-p, nil' will appear in the minibuffer. The problem is that `blink-cursor-callback' no longer has access to the global variable last-input-time (it is nil), so it runs into problems when it tries compare it as a number. The patch below to edit-utils/blink-cursor.el (as of xemacs-sumo-2001-04-08) appears to fix the problem. Could someone please apply it to the distribution? Thanks, -Ted ---8<--- $ diff -C3 blink-cursor.el-ORIG blink-cursor.el *** blink-cursor.el-ORIG Tue Apr 28 00:09:49 1998 --- blink-cursor.el Fri Jun 15 15:58:05 2001 *************** *** 43,49 **** (if (specifier-instance text-cursor-visible-p window) (if (let ((current-time (current-time))) ! (or (> (car current-time) (car last-input-time)) (> (cadr current-time) (cdr last-input-time)))) ;; turn cursor off only if more than a second since ;; last input --- 43,50 ---- (if (specifier-instance text-cursor-visible-p window) (if (let ((current-time (current-time))) ! (or (not last-input-time) ! (> (car current-time) (car last-input-time)) (> (cadr current-time) (cdr last-input-time)))) ;; turn cursor off only if more than a second since ;; last input