From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 58148@debbugs.gnu.org
Subject: bug#58148: 29.0.50; Wrong number of arguments in keymap-set--anon-cmacro
Date: Wed, 28 Sep 2022 22:34:44 +0300 [thread overview]
Message-ID: <86v8p72syz.fsf@mail.linkov.net> (raw)
In-Reply-To: <8735cbxspd.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 28 Sep 2022 20:24:46 +0200")
>> 1. Type in the *scratch*:
>>
>> (keymap-set g
>>
>> 2. Then 'completion-at-point' with 'M-C-i'.
>>
>> Debugger entered--Lisp error: (wrong-number-of-arguments (4 . 4) 2)
>
> I'm unable to reproduce the problem. Do you still see it after a "make
> bootstrap"?
Hmm, still fails after bootstrap in the latest master:
Debugger entered--Lisp error: (wrong-number-of-arguments #<subr keymap-set--anon-cmacro> 2)
keymap-set--anon-cmacro((keymap-set elisp--witness--lisp) elisp--witness--lisp)
In GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, X toolkit, cairo
version 1.16.0, Xaw3d scroll bars) of 2022-09-28
Repository revision: b6a163ba7cdf57eff5542b4cb6956780ebb2880f
Repository branch: master
next prev parent reply other threads:[~2022-09-28 19:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 18:03 bug#58148: 29.0.50; Wrong number of arguments in keymap-set--anon-cmacro Juri Linkov
2022-09-28 18:24 ` Lars Ingebrigtsen
2022-09-28 19:34 ` Juri Linkov [this message]
2022-09-29 10:34 ` Lars Ingebrigtsen
2022-09-29 15:30 ` Juri Linkov
2022-09-30 12:37 ` Lars Ingebrigtsen
2022-10-01 19:17 ` Juri Linkov
-- strict thread matches above, loose matches on Subject: below --
2022-10-09 16:20 bug#58396: 29.0.50; Optimization failure for add-to-list German Pacenza
2022-10-10 8:25 ` Lars Ingebrigtsen
2022-10-10 8:34 ` Lars Ingebrigtsen
2022-10-10 14:59 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-11 0:28 ` Lars Ingebrigtsen
2022-10-11 3:46 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-11 18:27 ` Lars Ingebrigtsen
2022-10-11 19:13 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-12 10:54 ` Lars Ingebrigtsen
2023-09-26 20:30 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-26 21:32 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-26 21:48 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-26 22:06 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-30 10:39 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-30 14:26 ` Eli Zaretskii
2023-09-30 18:51 ` bug#58148: 29.0.50; Wrong number of arguments in keymap-set--anon-cmacro Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-30 18:54 ` Eli Zaretskii
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=86v8p72syz.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=58148@debbugs.gnu.org \
--cc=larsi@gnus.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).