From: Eli Zaretskii <eliz@gnu.org>
To: 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: Sat, 03 Dec 2022 20:34:07 +0200 [thread overview]
Message-ID: <83mt84cp5s.fsf@gnu.org> (raw)
In-Reply-To: <83r0xgcpxj.fsf@gnu.org> (message from Eli Zaretskii on Sat, 03 Dec 2022 20:17:28 +0200)
> Cc: 59785@debbugs.gnu.org
> Date: Sat, 03 Dec 2022 20:17:28 +0200
> From: Eli Zaretskii <eliz@gnu.org>
>
> > From: Michael Heerdegen <michael_heerdegen@web.de>
> > Cc: 59785@debbugs.gnu.org
> > Date: Sat, 03 Dec 2022 18:53:07 +0100
> >
> > I checked again and: no, your change in subr.el has neither an effect in
> > behavior nor do I get a different backtrace.
>
> OK, thanks. Back to the drawing board...
Is it possible for you to see whether the org-capture case worked okay in
Emacs 28?
next prev parent reply other threads:[~2022-12-03 18:34 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 [this message]
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=83mt84cp5s.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 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.