From: Robert Pluim <rpluim@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: 59539@debbugs.gnu.org,
Ramesh Nedunchezian <rameshnedunchezian@outlook.com>
Subject: bug#59539: 29.0.50; Commands created with `insert-kbd-macro` are NOT getting repeated.
Date: Thu, 15 Dec 2022 10:45:21 +0100 [thread overview]
Message-ID: <87mt7pngpa.fsf@gmail.com> (raw)
In-Reply-To: <86tu1xjh1o.fsf@mail.linkov.net> (Juri Linkov's message of "Thu, 15 Dec 2022 09:20:31 +0200")
>>>>> On Thu, 15 Dec 2022 09:20:31 +0200, Juri Linkov <juri@linkov.net> said:
Ramesh> (defalias 'my-cmd-a
Ramesh> (kmacro "C-f C-f"))
>>
Ramesh> (defalias 'my-cmd-b
Ramesh> (kmacro "C-b C-b"))
>>
Ramesh> (define-key my-kmacro-keymap (kbd "a") #'my-cmd-a)
Ramesh> (define-key my-kmacro-keymap (kbd "b") #'my-cmd-b)
>>
>> Hmm, with your recipe on emacs master, "<f12> b" repeats, but "<f12>
>> a" doesnʼt. I have no clue why, they call the same underlying
>> infrastructure.
Juri> Sorry, I missed this bug report. This is because 'repeat-check-key'
Juri> is t by default so that unrelated key sequences, for example, 'C-_'
Juri> should not activate the repeat map for 'undo', only 'C-x u' should.
Juri> When the user types 'a', the real key from kmacro is 'C-f'.
Juri> There is no 'f' in the keymap above, so it's ignored,
Juri> when 'repeat-check-key' is not customized to nil.
That explains why '<f12> b' works
Juri> Do you have an idea how to do the right thing and to guess the user's
Juri> intention without checking if there are the same keys in the keymap?
I guess it should be possible to find out what the 'original' key
pressed was. <time passes> How about the below? I guess it changes the
behaviour when you have a command bound to two keys in the same repeat
map, and you use the 'wrong' one to repeat (but I could argue that
people creating such keymaps should use the 'repeat-check-key'
property)
Ramesh,
(put 'my-cmd-a 'repeat-check-key 'no)
(put 'my-cmd-b 'repeat-check-key 'no)
should do the right thing for you regardless of whether we change
Emacs.
Robert
--
diff --git a/lisp/repeat.el b/lisp/repeat.el
index 33e8d98ce3..05bdb5dfd1 100644
--- a/lisp/repeat.el
+++ b/lisp/repeat.el
@@ -458,8 +458,11 @@ repeat-post-hook
(when rep-map
(when (and (symbolp rep-map) (boundp rep-map))
(setq rep-map (symbol-value rep-map)))
- (let ((map (copy-keymap rep-map)))
-
+ (let* ((map (copy-keymap rep-map))
+ (internal (where-is-internal real-this-command (list map) t))
+ (real-key last-command-event))
+ (when internal
+ (setq real-key (aref internal 0)))
(when (and
;; Detect changes in the minibuffer state to allow repetitions
;; in the same minibuffer, but not when the minibuffer is activated
@@ -467,7 +470,7 @@ repeat-post-hook
(or (< (minibuffer-depth) (car repeat--prev-mb))
(eq current-minibuffer-command (cdr repeat--prev-mb)))
(or (not repeat-keep-prefix) prefix-arg)
- (repeat-check-key last-command-event map))
+ (repeat-check-key real-key map))
;; Messaging
(unless prefix-arg
next prev parent reply other threads:[~2022-12-15 9:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 10:58 bug#59539: 29.0.50; Commands created with `insert-kbd-macro` are NOT getting repeated Ramesh Nedunchezian
2022-12-14 17:13 ` Robert Pluim
2022-12-15 7:20 ` Juri Linkov
2022-12-15 9:45 ` Robert Pluim [this message]
2022-12-17 17:20 ` Juri Linkov
2022-12-27 9:19 ` Ramesh Nedunchezian
2022-12-27 18:06 ` Juri Linkov
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=87mt7pngpa.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=59539@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=rameshnedunchezian@outlook.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).