From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 59785@debbugs.gnu.org
Subject: bug#59785: 30.0.50; mouse-2 > (wrong-type-argument listp #<frame *Calendar* 0x...>)
Date: Sat, 03 Dec 2022 16:07:53 +0100 [thread overview]
Message-ID: <87r0xgplti.fsf@web.de> (raw)
In-Reply-To: <83359wegvc.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 03 Dec 2022 15:50:15 +0200")
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.
next prev parent reply other threads:[~2022-12-03 15:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 19:19 bug#59785: 30.0.50; mouse-2 > (wrong-type-argument listp #<frame *Calendar* 0x...>) Michael Heerdegen
2022-12-02 19:53 ` Eli Zaretskii
2022-12-02 20:00 ` Eli Zaretskii
2022-12-03 11:58 ` Michael Heerdegen
2022-12-03 12:04 ` Michael Heerdegen
2022-12-03 13:50 ` Eli Zaretskii
2022-12-03 15:07 ` Michael Heerdegen [this message]
2022-12-03 15:15 ` Eli Zaretskii
2022-12-03 17:22 ` Michael Heerdegen
2022-12-03 17:53 ` Michael Heerdegen
2022-12-03 18:17 ` Eli Zaretskii
2022-12-03 18:34 ` Eli Zaretskii
2022-12-03 19:46 ` Michael Heerdegen
2022-12-03 20:19 ` Michael Heerdegen
2022-12-04 6:19 ` Eli Zaretskii
2022-12-04 6:17 ` Eli Zaretskii
2022-12-04 22:03 ` Michael Heerdegen
2022-12-05 14:32 ` Eli Zaretskii
2022-12-05 19:15 ` Michael Heerdegen
2022-12-05 19:57 ` Eli Zaretskii
2022-12-03 18:03 ` Eli Zaretskii
2022-12-03 18:54 ` Michael Heerdegen
2022-12-03 19:27 ` Eli Zaretskii
2022-12-03 12:24 ` Eli Zaretskii
2022-12-03 14:58 ` Michael Heerdegen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r0xgplti.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=59785@debbugs.gnu.org \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.