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: Eli Zaretskii
Subject: bug#59785: 30.0.50; mouse-2 > (wrong-type-argument listp #<frame *Calendar* 0x...>)
Date: Sun, 04 Dec 2022 08:17:38 +0200

> 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.





reply via email to

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