Subject: Re: bug#73764: format-kbd-macro returns a key name that keymap-lookup doesn't recognize

From: Eli Zaretskii <[email-masked]>
Date: Mon, 14 Oct 2024 18:54:27 +0300

> From: Robert Pluim <[email-masked]>
> Cc: Andreas Schwab <[email-masked]>,  [email-masked],
>   [email-masked],  [email-masked]
> Date: Mon, 14 Oct 2024 17:06:05 +0200
> 
> >>>>> On Sat, 12 Oct 2024 18:18:18 +0300, Eli Zaretskii <[email-masked]> said:
> 
>     >> From: Andreas Schwab <[email-masked]>
>     >> Cc: Stefan Monnier <[email-masked]>,  [email-masked],
>     >> [email-masked]
>     >> 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')?

If that's the only case where we put C- in the wrong place, then
nothing stops us.  Is it?