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 12:58:26 +0100 [thread overview]
Message-ID: <874jucr95p.fsf@web.de> (raw)
In-Reply-To: <83wn79eftm.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 02 Dec 2022 22:00:37 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> > These commands seem to be trying to process a switch-frame event, not a
> > mouse-2 click event.
Could be.
> One possible solution is to make help--binding-undefined-p drop switch-frame
> events. Can you try that?
(How?)
But I don't think this is specific to help at all. So I guess this is
the wrong place to look for a fix, or at least not the only one.
What I did when I discovered the issue did not involve help: I tried to
select a date in the pop-up calendar for org-capture. It's hard to get
a backtrace for that scenario, though, but I can retry if that would
help.
Michael.
next prev parent reply other threads:[~2022-12-03 11:58 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 [this message]
2022-12-03 12:04 ` Michael Heerdegen
2022-12-03 13:50 ` Eli Zaretskii
2022-12-03 15:07 ` Michael Heerdegen
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=874jucr95p.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.