bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#59785: 30.0.50; mouse-2 > (wrong-type-argument listp #<frame *Calend


From: Michael Heerdegen
Subject: bug#59785: 30.0.50; mouse-2 > (wrong-type-argument listp #<frame *Calendar* 0x...>)
Date: Sat, 03 Dec 2022 16:07:53 +0100
User-agent: Gnus/5.13 (Gnus v5.13)

Eli Zaretskii <eliz@gnu.org> writes:

> Does the below fix this problem, per chance?
>
> diff --git a/lisp/subr.el b/lisp/subr.el
> index 21f4309..dc219a4 100644
> --- a/lisp/subr.el
> +++ b/lisp/subr.el
> @@ -1729,7 +1729,7 @@ posn-col-row
>       ((eq area 'horizontal-scroll-bar)
>        (cons (scroll-bar-scale pair (window-width window)) 0))
>       (t
> -      (if use-window
> +      (if (and (windowp frame-or-window) use-window)
>            (cons (/ (car pair) (window-font-width window))
>                  (/ (cdr pair) (window-font-height window)))
>          ;; FIXME: This should take line-spacing properties on

Half: it improves the behavior but I still get the error.  The
improvement is that I can successfully select a date in the calendar
despite the error - that was not possible without that change.  So I
guess the error now happens at some other place, and this was not the
root, or not the only root.

I also tested this:

modified   lisp/mouse-drag.el
@@ -287,8 +287,10 @@ mouse-drag-drag
       (while (progn
               (setq event (read--potential-mouse-event)
                     end (event-end event)
-                    row (cdr (posn-col-row end))
-                    col (car (posn-col-row end)))
+                    row (and (not (eq (car-safe event) 'switch-frame))
+                              (cdr (posn-col-row end)))
+                    col (and (not (eq (car-safe event) 'switch-frame))
+                              (car (posn-col-row end))))
               (or (mouse-movement-p event)
                   (eq (car-safe event) 'switch-frame)))
        ;; Scroll if see if we're on the edge.

It actually had the exact same effect.

Michael.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]