all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Sun, 04 Dec 2022 23:03:02 +0100	[thread overview]
Message-ID: <87359ultd5.fsf@web.de> (raw)
In-Reply-To: <83bkojd75p.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 04 Dec 2022 08:17:38 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> So if you cannot reproduce the org-capture case in "emacs -Q", perhaps
> some other recipe which causes the same backtrace can be reproduced?

I tried all day and we are lucky, I finally found a recipe for emacs -Q,
and it seems indeed to be a regression from at least 27.1:

#+begin_src emacs-lisp
  (require 'org)
  (require 'calendar)

  (setq org-read-date-popup-calendar t)
  (setq calendar-setup 'calendar-only)

  ;; my probably a bit non-standard setup:
  (global-set-key [down-mouse-2] #'mouse-drag-drag)
  (define-key calendar-mode-map [down-mouse-2] nil)

  (setq debug-on-error t)
  ;; this is only to allow to switch to the
  ;; Debugger despite of the active minibuffer
  (setq enable-recursive-minibuffers t)

  ;; Now select a date with mouse-2 in the calendar after
  ;; evaluating this:
  (org-read-date)
  ;; then switch to the debugger buffer (e.g. with C-x C-b)
#+end_src

This gives me:

| Debugger entered--Lisp error: (wrong-type-argument listp #<frame  *Minibuf-1* 0x56442ad52540>)
|   posn-col-row(#<frame  *Minibuf-1* 0x56442ad52540>)
|   #f(compiled-function () #<bytecode -0x1fa7ba0046068077>)()
|   internal--track-mouse(#f(compiled-function () #<bytecode -0x1fa7ba0046068077>))
|   mouse-drag-drag((down-mouse-2 (#<window 8 on *Calendar*> 499 (334 . 123) 89797497 nil 499 (37 . 6) nil (1 . 15) (9 . 18))))
|   funcall-interactively(mouse-drag-drag (down-mouse-2 (#<window 8 on *Calendar*> 499 (334 . 123) 89797497 nil 499 (37 . 6) nil (1 . 15) (9 . 18))))
|   call-interactively(mouse-drag-drag nil nil)
|   command-execute(mouse-drag-drag)
|   read-string("Date+time [2022-12-04]: " nil org-read-date-history nil)
|   org-read-date()
|   eval-buffer()  ; Reading at buffer position 677
|   funcall-interactively(eval-buffer)
|   call-interactively(eval-buffer record nil)
|   command-execute(eval-buffer record)
|   execute-extended-command(nil "eval-buffer" "eval-buffer")
|   funcall-interactively(execute-extended-command nil "eval-buffer" "eval-buffer")
|   call-interactively(execute-extended-command nil nil)
|   command-execute(execute-extended-command)


Michael.





  reply	other threads:[~2022-12-04 22: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 [this message]
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=87359ultd5.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.