unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: 47785@debbugs.gnu.org
Subject: bug#47785: 28.0.50; kmacro-edit-lossage fails when \C-hl is not bound to view-lossage
Date: Tue, 04 May 2021 12:48:20 +0200	[thread overview]
Message-ID: <87k0oe93m3.fsf@gnus.org> (raw)
In-Reply-To: <874kg8ci8j.fsf@localhost> (Ihor Radchenko's message of "Thu, 15 Apr 2021 11:57:32 +0800")

Ihor Radchenko <yantar92@gmail.com> writes:

> I just encountered error trying to run C-x C-k l (kmacro-edit-lossage).
> The error was "Key sequence C-h l is not defined".
>
> The reason is my personal key bindings. I have rebound C-h key to some
> other command as there is <F1>- prefix to do the same thing anyway.
>
> However, breakage of kmacro-edit-lossage is unexpected. I do not think
> that it should depend on the C-h l to be bound to view-lossage.

I can confirm that

(global-set-key "\C-hl" 'undefined)
C-x C-k l

then signals an error.  But I'm getting

Debugger entered--Lisp error: (error "Key sequence C-h l is not a keyboard macro")

in Emacs 28.

I've just taken a very quick look at the command, and I'm guessing it
has something to do with:

	    ((or (memq cmd '(view-lossage electric-view-lossage))
                 (memq cmd-noremap '(view-lossage electric-view-lossage)))
	     (setq mac (recent-keys))

mac ends up being

#<subr undefined>

which leads to bugging out.  Does anybody immediately see what this code
is supposed to do here, and can fix this?  If not, I'll poke at it some
more tomorrow; no more time today.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-05-04 10:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-15  3:57 bug#47785: 28.0.50; kmacro-edit-lossage fails when \C-hl is not bound to view-lossage Ihor Radchenko
2021-05-04 10:48 ` Lars Ingebrigtsen [this message]
2021-05-05 13:00   ` Lars Ingebrigtsen
2021-05-11  4:06     ` Ihor Radchenko

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=87k0oe93m3.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=47785@debbugs.gnu.org \
    --cc=yantar92@gmail.com \
    /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).