From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 59785@debbugs.gnu.org
Subject: bug#59785: 30.0.50; mouse-2 > (wrong-type-argument listp #<frame *Calendar* 0x...>)
Date: Sun, 04 Dec 2022 08:17:38 +0200 [thread overview]
Message-ID: <83bkojd75p.fsf@gnu.org> (raw)
In-Reply-To: <877cz8l176.fsf@web.de> (message from Michael Heerdegen on Sat, 03 Dec 2022 20:46:53 +0100)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: 59785@debbugs.gnu.org
> Date: Sat, 03 Dec 2022 20:46:53 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Is it possible for you to see whether the org-capture case worked okay
> > in Emacs 28?
>
> I have 27. Would that suffice?
It's better than nothing. I want to know if this problem happens because of
recent changes in various posn-* functions. It will help me identify the
culprit if there is one (as opposed to if this is an old problem that no one
bothered to report).
> I tried to load anything that seemed related but the issue is not
> reproducible so far :-(
Too bad. I'd like to have a way of reproducing this here, because I have
difficulty understanding the data and backtraces you posted. Specifically,
I don't understand which code signals an error, what data triggers that, and
how the data which triggers the error is related to the switch-frame event
in the first place.
The "C-h k" case should be already fixed (by "other means"), so it cannot
help me anymore. In any case, these two cases only share one thing in
common: that the switch-frame event was delivered to functions that didn't
expect it. Everything else is different.
So if you cannot reproduce the org-capture case in "emacs -Q", perhaps some
other recipe which causes the same backtrace can be reproduced?
Thanks.
next prev parent reply other threads:[~2022-12-04 6:17 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
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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83bkojd75p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59785@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).