unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Sat, 03 Dec 2022 20:03:11 +0200	[thread overview]
Message-ID: <83tu2ccqlc.fsf@gnu.org> (raw)
In-Reply-To: <87mt84pfld.fsf@web.de> (message from Michael Heerdegen on Sat, 03 Dec 2022 18:22:22 +0100)

> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: 59785@debbugs.gnu.org
> Date: Sat, 03 Dec 2022 18:22:22 +0100
> 
> Ok, so we have now different scenarios and different proposed cures.
> What concretely would help further?

I still don't think I have the answer to my question: was the backtrace
exactly the same with the patch I sent, or was it different?  I'm asking
about the org-capture case, not about the "C-h k" case.  It is important for
me to know whether the patch I sent solves part of the problem or nothing at
all.

> Did you try to reproduce the problem btw?

I can reproduce the "C-h k" case, which is why I'm asking about the other
one.





  parent reply	other threads:[~2022-12-03 18:03 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
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 [this message]
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=83tu2ccqlc.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).