unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Hutcheson via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, 54027@debbugs.gnu.org
Subject: bug#54027: Wishlist: Support full CSI u specification for terminal input
Date: Tue, 24 May 2022 21:25:03 -0400	[thread overview]
Message-ID: <CACjgaUfCihp=y98U7dcfD16y9S2K1uvU6P4X=qNA=00yXmRNuw@mail.gmail.com> (raw)
In-Reply-To: <jwvzgmbvwu4.fsf-monnier+emacs@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]

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 <monnier@iro.umontreal.ca>
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
>
>

[-- Attachment #2: Type: text/html, Size: 1505 bytes --]

  reply	other threads:[~2022-05-25  1:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 18:24 bug#54027: Wishlist: Support full CSI u specification for terminal input Alex Hutcheson via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-17 23:14 ` Richard Stallman
2022-02-18  8:30 ` Eli Zaretskii
2022-02-23  1:07   ` Alex Hutcheson via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-26  8:10     ` Eli Zaretskii
2022-02-27 18:21       ` Alex Hutcheson via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-27 18:38         ` Eli Zaretskii
2022-02-27 18:53           ` Alex Hutcheson via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-27 19:16             ` Eli Zaretskii
2022-02-28  3:49         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-28 12:17           ` Eli Zaretskii
2022-02-28 13:22             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-28 13:31               ` Eli Zaretskii
2022-02-28 15:25                 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-25  1:25                   ` Alex Hutcheson via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-05-25  2:33                     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors

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='CACjgaUfCihp=y98U7dcfD16y9S2K1uvU6P4X=qNA=00yXmRNuw@mail.gmail.com' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=54027@debbugs.gnu.org \
    --cc=alexhutcheson@google.com \
    --cc=eliz@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).