From: Juri Linkov <juri@linkov.net>
To: 49953@debbugs.gnu.org
Subject: bug#49953: 28.0.50; tmm is broken on compiled menus
Date: Mon, 09 Aug 2021 10:12:28 +0300 [thread overview]
Message-ID: <87im0fhz1f.fsf@mail.linkov.net> (raw)
0. emacs -Q
1. Eval: (tmm-prompt (mouse-buffer-menu-keymap))
2. Select a menu item with the mouse click
from the *Completions* buffer
3. It fails with this backtrace:
Debugger entered--Lisp error: (error "Empty menu reached")
error("Empty menu reached")
tmm-prompt((keymap "Select Buffer" [("*scratch* * " . #f(compiled-function () (interactive nil) #<bytecode...
tmm-prompt((keymap (Select\ Buffer "Select Buffer" keymap ...
(progn (tmm-prompt (mouse-buffer-menu-keymap)))
eval((progn (tmm-prompt (mouse-buffer-menu-keymap))) t)
elisp--eval-last-sexp((4))
eval-last-sexp((4))
funcall-interactively(eval-last-sexp (4))
call-interactively(eval-last-sexp nil nil)
command-execute(eval-last-sexp)
This regression began to occur after merging native-compilation.
It seems the problem is that tmm-get-keymap does very strange things:
(cond ((if (listp elt)
(or (keymapp elt) (eq (car elt) 'lambda))
(and (symbolp elt) (fboundp elt)))
I don't know why it checks for 'lambda' and 'symbolp',
but such checks fail on a compiled function.
next reply other threads:[~2021-08-09 7:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 7:12 Juri Linkov [this message]
2021-08-09 13:20 ` bug#49953: 28.0.50; tmm is broken on compiled menus Lars Ingebrigtsen
2021-08-09 17:09 ` Eli Zaretskii
2021-08-09 18:23 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87im0fhz1f.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=49953@debbugs.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 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).