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: Sat, 03 Dec 2022 19:54:04 +0100 [thread overview]
Message-ID: <87bkokl3n7.fsf@web.de> (raw)
In-Reply-To: <83tu2ccqlc.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 03 Dec 2022 20:03:11 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> 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.
You should have been clearer what case you are interested in.
But I answered it: no difference. The backtraces look exactly the same,
apart from details (depending on where I clicked).
AFAIU, in the case of the error your change doesn't make a difference
because the argument is a frame, not a window (last call below, these
are all calls to the function done in one reproduction of the recipe):
| 1 -> (posn-col-row (#<window 26 on *Calendar*> 419 ... 31213232 nil 419 ... nil ... ...)) 19:48:18.661
| (mouse-drag-drag (down-mouse-2 (#<window 26 on *Calendar*> 419 (478 . 158) 31213232 nil 419 (34 . 5) nil (2 . 18) (14 . 28))))
| (command-execute mouse-drag-drag)
| (my-read-string--default-in-prompt-around-ad #<subr read-string> "Date+time [2022-12-03]: " nil org-read-date-history nil)
| (org-read-date nil t nil nil)
| (org-capture-fill-template)
| (my-org-capture--around-ad #f(compiled-function (&optional goto keys) "Capture something.\n\\<org-capture-mode-map>\nThis will let you select a template from `org-capture-templates', and\nthen file the newly captured information. The text is immediately\ninserted at the target location, and an indirect buffer is shown where\nyou can edit it. Pressing `\\[org-capture-finalize]' brings you back to the previous\nstate of Emacs, so that you can continue your work.\n\nWhen called interactively with a `\\[universal-argument]' prefix argument GOTO, don't\ncapture anything, just go to the file/headline where the selected\ntemplate stores its notes.\n\nWith a `\\[universal-argument] \\[universal-argument]' prefix argument, go to the last note stored.\n\nWhen called with a `C-0' (zero) prefix, insert a template at point.\n\nWhen called with a `C-1' (one) prefix, force prompting for a date when\na datetree entry is made.\n\nELisp programs can set KEYS to a string associated with a template\nin `org-capture-templates'. In this case, interactive selection\nwill be bypassed.\n\nIf `org-capture-use-agenda-date' is non-nil, capturing from the\nagenda will use the date at point as the default date. Then, a\n`C-1' prefix will tell the capture process to use the HH:MM time\nof the day at point (if any) or the current HH:MM time." (interactive "P") #<bytecode -0x1e2ea2230cf83a5>) nil)
| (org-capture nil)
| (command-execute org-capture)
| 1 <- posn-col-row: (34 . 5)
| 1 -> (posn-col-row (#<window 26 on *Calendar*> 419 ... 31213232 nil 419 ... nil ... ...)) 19:48:19.087
| (mouse-drag-drag (down-mouse-2 (#<window 26 on *Calendar*> 419 (478 . 158) 31213232 nil 419 (34 . 5) nil (2 . 18) (14 . 28))))
| (command-execute mouse-drag-drag)
| (my-read-string--default-in-prompt-around-ad #<subr read-string> "Date+time [2022-12-03]: " nil org-read-date-history nil)
| (org-read-date nil t nil nil)
| (org-capture-fill-template)
| (my-org-capture--around-ad #f(compiled-function (&optional goto keys) "Capture something.\n\\<org-capture-mode-map>\nThis will let you select a template from `org-capture-templates', and\nthen file the newly captured information. The text is immediately\ninserted at the target location, and an indirect buffer is shown where\nyou can edit it. Pressing `\\[org-capture-finalize]' brings you back to the previous\nstate of Emacs, so that you can continue your work.\n\nWhen called interactively with a `\\[universal-argument]' prefix argument GOTO, don't\ncapture anything, just go to the file/headline where the selected\ntemplate stores its notes.\n\nWith a `\\[universal-argument] \\[universal-argument]' prefix argument, go to the last note stored.\n\nWhen called with a `C-0' (zero) prefix, insert a template at point.\n\nWhen called with a `C-1' (one) prefix, force prompting for a date when\na datetree entry is made.\n\nELisp programs can set KEYS to a string associated with a template\nin `org-capture-templates'. In this case, interactive selection\nwill be bypassed.\n\nIf `org-capture-use-agenda-date' is non-nil, capturing from the\nagenda will use the date at point as the default date. Then, a\n`C-1' prefix will tell the capture process to use the HH:MM time\nof the day at point (if any) or the current HH:MM time." (interactive "P") #<bytecode -0x1e2ea2230cf83a5>) nil)
| (org-capture nil)
| (command-execute org-capture)
| 1 <- posn-col-row: (34 . 5)
| 1 -> (posn-col-row #<frame *Minibuf-1* micha@drachen 0x56052a407bd8>) 19:48:19.161
| (mouse-drag-drag (down-mouse-2 (#<window 26 on *Calendar*> 419 (478 . 158) 31213232 nil 419 (34 . 5) nil (2 . 18) (14 . 28))))
| (command-execute mouse-drag-drag)
| (my-read-string--default-in-prompt-around-ad #<subr read-string> "Date+time [2022-12-03]: " nil org-read-date-history nil)
| (org-read-date nil t nil nil)
| (org-capture-fill-template)
| (my-org-capture--around-ad #f(compiled-function (&optional goto keys) "Capture something.\n\\<org-capture-mode-map>\nThis will let you select a template from `org-capture-templates', and\nthen file the newly captured information. The text is immediately\ninserted at the target location, and an indirect buffer is shown where\nyou can edit it. Pressing `\\[org-capture-finalize]' brings you back to the previous\nstate of Emacs, so that you can continue your work.\n\nWhen called interactively with a `\\[universal-argument]' prefix argument GOTO, don't\ncapture anything, just go to the file/headline where the selected\ntemplate stores its notes.\n\nWith a `\\[universal-argument] \\[universal-argument]' prefix argument, go to the last note stored.\n\nWhen called with a `C-0' (zero) prefix, insert a template at point.\n\nWhen called with a `C-1' (one) prefix, force prompting for a date when\na datetree entry is made.\n\nELisp programs can set KEYS to a string associated with a template\nin `org-capture-templates'. In this case, interactive selection\nwill be bypassed.\n\nIf `org-capture-use-agenda-date' is non-nil, capturing from the\nagenda will use the date at point as the default date. Then, a\n`C-1' prefix will tell the capture process to use the HH:MM time\nof the day at point (if any) or the current HH:MM time." (interactive "P") #<bytecode -0x1e2ea2230cf83a5>) nil)
| (org-capture nil)
| (command-execute org-capture)
| 1 <- posn-col-row: !non-local\ exit!
Michael.
next prev parent reply other threads:[~2022-12-03 18:54 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
2022-12-03 18:54 ` Michael Heerdegen [this message]
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=87bkokl3n7.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.