bug#58148: 29.0.50; Wrong number of arguments in keymap-set--anon-cmacro

bug#58148: 29.0.50; Wrong number of arguments in keymap-set--anon-cmacro

[Juri Linkov]

0. emacs -Q
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)
  keymap-set--anon-cmacro((keymap-set elisp--witness--lisp) elisp--witness--lisp)
  apply(keymap-set--anon-cmacro (keymap-set elisp--witness--lisp) elisp--witness--lisp)
  macroexp--compiler-macro(keymap-set--anon-cmacro (keymap-set elisp--witness--lisp))
  #f(compiled-function (form func) #<bytecode -0x1997929cc4a97ca0>)(((keymap-set elisp--witness--lisp)) keymap-set)
  macroexp--expand-all((keymap-set elisp--witness--lisp))
  macroexpand-all((keymap-set elisp--witness--lisp))
  elisp--local-variables()
  #f(compiled-function (string) #<bytecode -0x5dd040ab2d900d4>)(#("g" 0 1 (fontified t rear-nonsticky t)))
  #f(compiled-function (string pred action) #<bytecode -0x131cb872953b2efd>)(#("g" 0 1 (fontified t rear-nonsticky t)) nil nil)
  try-completion(#("g" 0 1 (fontified t rear-nonsticky t)) #f(compiled-function (string pred action) #<bytecode -0x131cb872953b2efd>) nil)
  #f(compiled-function (table) #<bytecode 0x1635acab3bc82542>)(#f(compiled-function (string pred action) #<bytecode -0x131cb872953b2efd>))
  mapcar(#f(compiled-function (table) #<bytecode 0x1635acab3bc82542>) (#f(compiled-function (string pred action) #<bytecode -0x131cb872953b2efd>) #f(compiled-function (&rest args2) #<bytecode -0x12a9d92cb5a883a4>)))
  #f(compiled-function (string pred action) #<bytecode 0x59c9db15e8e1ece>)(#("g" 0 1 (fontified t rear-nonsticky t)) nil nil)
  try-completion(#("g" 0 1 (fontified t rear-nonsticky t)) #f(compiled-function (string pred action) #<bytecode 0x59c9db15e8e1ece>) nil)
  completion-basic-try-completion(#("g" 0 1 (rear-nonsticky t fontified t)) #f(compiled-function (string pred action) #<bytecode 0x59c9db15e8e1ece>) nil 1)
  #f(compiled-function (style) #<bytecode 0x178271f9e5e4c041>)(basic)
  completion--some(#f(compiled-function (style) #<bytecode 0x178271f9e5e4c041>) (basic partial-completion emacs22))
  completion--nth-completion(1 #("g" 0 1 (rear-nonsticky t fontified t)) #f(compiled-function (string pred action) #<bytecode 0x59c9db15e8e1ece>) nil 1 (metadata))
  completion-try-completion(#("g" 0 1 (rear-nonsticky t fontified t)) #f(compiled-function (string pred action) #<bytecode 0x59c9db15e8e1ece>) nil 1 (metadata))
  completion--do-completion(#<marker at 158 in *scratch*> 159)
  completion--in-region-1(#<marker at 158 in *scratch*> 159)
  #f(compiled-function (start end collection predicate) #<bytecode -0xceba54d1e8420a4>)(#<marker at 158 in *scratch*> 159 #f(compiled-function (string pred action) #<bytecode 0x59c9db15e8e1ece>) nil)
  apply(#f(compiled-function (start end collection predicate) #<bytecode -0xceba54d1e8420a4>) (#<marker at 158 in *scratch*> 159 #f(compiled-function (string pred action) #<bytecode 0x59c9db15e8e1ece>) nil))
  #f(compiled-function (funs global args) #<bytecode -0xf63b519da3ae62>)(nil nil (#<marker at 158 in *scratch*> 159 #f(compiled-function (string pred action) #<bytecode 0x59c9db15e8e1ece>) nil))
  completion--in-region(#<marker at 158 in *scratch*> 159 #f(compiled-function (string pred action) #<bytecode 0x59c9db15e8e1ece>) nil)
  completion-in-region(#<marker at 158 in *scratch*> 159 #f(compiled-function (string pred action) #<bytecode 0x59c9db15e8e1ece>) nil)
  completion-at-point()
  funcall-interactively(completion-at-point)
  command-execute(completion-at-point)

bug#58148: 29.0.50; Wrong number of arguments in keymap-set--anon-cmacro

[Lars Ingebrigtsen]

Juri Linkov <juri@linkov.net> writes:

> 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"?

bug#58148: 29.0.50; Wrong number of arguments in keymap-set--anon-cmacro

[Juri Linkov]

>> 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

bug#58148: 29.0.50; Wrong number of arguments in keymap-set--anon-cmacro

[Lars Ingebrigtsen]

Juri Linkov <juri@linkov.net> writes:

> 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)

There was another report of something similar, but that seemed to have
something to do with previously compiled packages, which is why I
thought this might be a stale .elc problem.

I'm wondering why I'm not seeing the issue then -- I tried a "make
bootstrap" and then "emacs -Q" and the recipe, and didn't get any errors.

> 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

I've got:

In GNU Emacs 29.0.50 (build 41, x86_64-pc-linux-gnu, GTK+ Version
 3.24.33, cairo version 1.16.0) of 2022-09-28 built on joga
Repository revision: 1254d9a3ae89697b591343de2ddf55c5879bc937
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12101003
System Description: Ubuntu 22.04.1 LTS

Could possibly a toolkit version make any difference here?  That would
be really weird.

Hm...  anybody have any ideas?

bug#58148: 29.0.50; Wrong number of arguments in keymap-set--anon-cmacro

[Juri Linkov]

>> 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)
>
> There was another report of something similar, but that seemed to have
> something to do with previously compiled packages, which is why I
> thought this might be a stale .elc problem.
>
> I'm wondering why I'm not seeing the issue then -- I tried a "make
> bootstrap" and then "emacs -Q" and the recipe, and didn't get any errors.

Sorry, I had an additional setting more than -Q:

  (setq debug-on-error t)

I thought it's required to see errors in -Q, because without
debug-on-error, the errors are hidden in *Messages*. And
indeed in this case without debug-on-error *Messages* contains:

  Warning: Optimization failure for keymap-set: Handler: keymap-set--anon-cmacro
  (wrong-number-of-arguments #<subr keymap-set--anon-cmacro> 2)
  Making completion list...

bug#58148: 29.0.50; Wrong number of arguments in keymap-set--anon-cmacro

[Lars Ingebrigtsen]

Juri Linkov <juri@linkov.net> writes:

> Sorry, I had an additional setting more than -Q:
>
>   (setq debug-on-error t)
>
> I thought it's required to see errors in -Q, because without
> debug-on-error, the errors are hidden in *Messages*. And
> indeed in this case without debug-on-error *Messages* contains:
>
>   Warning: Optimization failure for keymap-set: Handler: keymap-set--anon-cmacro
>   (wrong-number-of-arguments #<subr keymap-set--anon-cmacro> 2)
>   Making completion list...

Still not seeing the problem, unfortunately --

emacs -Q
M-: (setq debug-on-error t)

(keymap-set d `C-M-i'

No errors, and nothing in *Messages*, with or without debug-on-error.

bug#58148: 29.0.50; Wrong number of arguments in keymap-set--anon-cmacro

[Juri Linkov]

>>   Warning: Optimization failure for keymap-set: Handler: keymap-set--anon-cmacro
>>   (wrong-number-of-arguments #<subr keymap-set--anon-cmacro> 2)
>
> Still not seeing the problem, unfortunately --
>
> emacs -Q
> M-: (setq debug-on-error t)
>
> (keymap-set d `C-M-i'
>
> No errors, and nothing in *Messages*, with or without debug-on-error.

I tried again to bootstrap with extra clean, but still the same error.
We need someone to try this out too that could help to clarify
where is the problem 🧐

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]

Eli Zaretskii <eliz@gnu.org> writes:

> Most of this comment should be in the commit log message, I think, and
> the [1] and [3] markers should be replaced with text telling what that
> does.  Otherwise, the first patch is okay for the emacs-29 branch.

Updated the patch accordingly and sent it on that other branch of this
thread, please review.  However, I removed the [1] and [3] markers
without replacement: I don't think that there is much need to separately
comment on a `condition-case' or a let-binding of `inhibit-message'.

> Regarding the second patch: if Stefan Monnier and Stefan Kangas are
> okay with it, so am I.

Does that mean that I should explicitly draw Stefan Kangas' attention to
this bug?  Or would he notice somehow otherwise?

Thanks.

bug#58148: 29.0.50; Wrong number of arguments in keymap-set--anon-cmacro

[Eli Zaretskii]

> From: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
> Cc: 58148@debbugs.gnu.org,  germanp82@hotmail.com,  58396@debbugs.gnu.org,
>   larsi@gnus.org,  monnier@iro.umontreal.ca
> Date: Sat, 30 Sep 2023 20:51:25 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Most of this comment should be in the commit log message, I think, and
> > the [1] and [3] markers should be replaced with text telling what that
> > does.  Otherwise, the first patch is okay for the emacs-29 branch.
> 
> Updated the patch accordingly and sent it on that other branch of this
> thread, please review.

It's fine, thanks.

> > Regarding the second patch: if Stefan Monnier and Stefan Kangas are
> > okay with it, so am I.
> 
> Does that mean that I should explicitly draw Stefan Kangas' attention to
> this bug?  Or would he notice somehow otherwise?

Just wait for him to chime in, which will happen soon enough.