Subject: bug#54027: Wishlist: Support full CSI u specification for terminal input

From: Alex Hutcheson <[email-masked]>
Date: Tue, 24 May 2022 21:25:03 -0400

Was a consensus ever reached on this?

Stefan's patch looks like it does what I was asking for.

It would be great if we could also handle the `ESC [ ... u` versions,
because xterm will emit them in
some configurations, and iTerm2 can only emit those.

On Mon, Feb 28, 2022 at 10:25 AM Stefan Monnier <[email-masked]>
wrote:

> > Then I must be missing something.  Do you mean this part:
> >
> >   +    (while (<= #x30 final #x3F)
> >   +      (push final params) ;And read more.
> >   +      (setq final (read-char)))
> >   +    (while (<= #x20 final #x2F)
> >   +      (push final intermediates)
> >   +      (setq final (read-char)))
> >
> > This doesn't add all the 96 characters with the modifiers, it only
> > adds the digits and the punctuation characters.
>
> The above just reads to "NN;MM" part of the escape sequence which
> encodes in decimal the Unicode code point MM of the character and the
> 4bit encoded NN of the modifiers shift, alt, control, and meta.
>
>
>         Stefan
>
>