From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 73764@debbugs.gnu.org, Andreas Schwab <schwab@linux-m68k.org>,
monnier@iro.umontreal.ca, eduardoochs@gmail.com
Subject: bug#73764: format-kbd-macro returns a key name that keymap-lookup doesn't recognize
Date: Mon, 14 Oct 2024 17:06:05 +0200 [thread overview]
Message-ID: <87cyk2u3ky.fsf@gmail.com> (raw)
In-Reply-To: <86y12tuz7p.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 12 Oct 2024 18:18:18 +0300")
>>>>> On Sat, 12 Oct 2024 18:18:18 +0300, Eli Zaretskii <eliz@gnu.org> said:
>> From: Andreas Schwab <schwab@linux-m68k.org>
>> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 73764@debbugs.gnu.org,
>> eduardoochs@gmail.com
>> Date: Sat, 12 Oct 2024 16:51:49 +0200
>>
>> On Okt 12 2024, Eli Zaretskii wrote:
>>
>> >> I guess we also need to make sure `format-kbd-macro` generates
>> >> something that `key-valid-p` accepts.
>> >
>> > AFAICS, that's impossible without completely rewriting its code. It
>> > proceeds from left to right (i.e. from MSB to LSB).
>>
>> The issue here is that C-h is a character on its own, unlike, say, C-+.
Eli> Right. And in that case, the C- prefix is generated when a control
Eli> character is seen, which is at the end.
So if format-kbd-macro generates something with 'C-' in the "wrong"
place, whatʼs to stop us re-ordering the modifiers as a
post-processing step (inside `format-kbd-macro')?
Robert
--
next prev parent reply other threads:[~2024-10-14 15:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-12 4:46 bug#73764: format-kbd-macro returns a key name that keymap-lookup doesn't recognize Eduardo Ochs
2024-10-12 9:18 ` Eli Zaretskii
2024-10-12 13:33 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-12 14:36 ` Eli Zaretskii
2024-10-12 14:51 ` Andreas Schwab
2024-10-12 15:18 ` Eli Zaretskii
2024-10-14 15:06 ` Robert Pluim [this message]
2024-10-14 15:54 ` Eli Zaretskii
2024-10-14 16:25 ` Eli Zaretskii
2024-10-14 21:48 ` Stefan Kangas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cyk2u3ky.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=73764@debbugs.gnu.org \
--cc=eduardoochs@gmail.com \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@linux-m68k.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.