bug#61647: closed (edit-kbd-macro: Wrong type argument: characterp, 134217785)

[GNU bug Tracking System]

Your message dated Mon, 20 Feb 2023 13:18:33 +0100
with message-id <EB8849C0-9628-43A8-9258-905C8CDAB88D@acm.org>
and subject line Re: bug#61647: edit-kbd-macro: Wrong type argument: 
characterp, 134217785
has caused the debbugs.gnu.org bug report #61647,
regarding edit-kbd-macro: Wrong type argument: characterp, 134217785
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
61647: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=61647
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: edit-kbd-macro: Wrong type argument: characterp, 134217785 Date: Mon, 20 Feb 2023 02:31:25 -0300

Hi all, I found a keyboard macro on which edit-kbd-macro fails with
this error:

  edit-kbd-macro: Wrong type argument: characterp, 134217785

To reproduce the error run any of these two setqs - they should be
equivalent -

  (setq last-kbd-macro [134217847 134217785 134217785 134217834 5 32
    25 1 67108896 down 134217847 134217777 134217834 return 25
    134217803 134217803])

  (setq last-kbd-macro (kbd "M-w M-99 M-j C-e SPC C-y C-a C-SPC <down>
    M-w M-1 M-j RET C-y 2*M-K"))

and then run `M-x edit-kbd-macro C-x e'.

The error happens in this version of Emacs,

  GNU Emacs 30.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version
  3.24.24, cairo version 1.16.0) of 2023-02-20

but not in an Emacs28. Here's the output of uname -a:

  Linux scylla 5.10.0-21-amd64 #1 SMP Debian 5.10.162-1 (2023-01-21)
  x86_64 GNU/Linux

Cheers,

  Eduardo Ochs

  http://anggtwu.net/#eev

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#61647: edit-kbd-macro: Wrong type argument: characterp, 134217785
>
>
>
>
> Date: 
>
> Mon, 20 Feb 2023 13:18:33 +0100
>
>
>
>
> 20 feb. 2023 kl. 12.39 skrev Daniel Martín <mardani29@yahoo.es>:
>
> > This is the commit that introduced this regression:
>
> Sorry about that mistake, and thank you very much for finding it!
> Now fixed on master.
>
>
>
> --- End Message ---