From: Eli Zaretskii <eliz@gnu.org>
To: Len Trigg <lenbok@gmail.com>
Cc: 60077@debbugs.gnu.org
Subject: bug#60077: 29.0.60; Is xterm modifyOtherKeys support broken?
Date: Thu, 15 Dec 2022 11:10:39 +0200 [thread overview]
Message-ID: <83ilidkp68.fsf@gnu.org> (raw)
In-Reply-To: <CAOGVwenTm5acGVj0G-K6NWfEXNmRsRoVUWob3E5XnqRuxb5S_Q@mail.gmail.com> (message from Len Trigg on Thu, 15 Dec 2022 21:57:00 +1300)
> From: Len Trigg <lenbok@gmail.com>
> Date: Thu, 15 Dec 2022 21:57:00 +1300
> Cc: 60077@debbugs.gnu.org
>
> On Thu, 15 Dec 2022 at 21:38, Len Trigg <lenbok@gmail.com> wrote:
>
> Do you think it's just a matter of the dolist on line 466 of xterm.el needing additional entries (I don't see
> one there for M-SPC)?
>
> For example, I see there looks to be an entry for C-M-SPC:
> (7 32 [?\C-\M-\s])
> And my wild speculation from looking at the example table "Other modified-key escapes" on
> https://invisible-island.net/xterm/modified-keys-us-pc105.html is that emacs would need an entry like:
> (3 32 [?\M-\s])
> to handle the modifyOtherKeys encoding of "\E[27;3;32~" for M-SPC,
If that fixes the problem, we could install it.
> but also that there are probably
> many many other sequences that aren't being handled.
There's nothing wrong with solving this one problem at a time, right?
Especially since we don't seem to have complaints about other
sequences.
next prev parent reply other threads:[~2022-12-15 9:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 21:48 bug#60077: 29.0.60; Is xterm modifyOtherKeys support broken? Len Trigg
2022-12-15 6:41 ` Eli Zaretskii
2022-12-15 8:38 ` Len Trigg
2022-12-15 8:57 ` Len Trigg
2022-12-15 9:10 ` Eli Zaretskii [this message]
2022-12-15 19:48 ` Len Trigg
2022-12-16 6:52 ` Eli Zaretskii
2022-12-16 7:40 ` Eli Zaretskii
2022-12-16 16:04 ` Eli Zaretskii
2022-12-15 9:06 ` Eli Zaretskii
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=83ilidkp68.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60077@debbugs.gnu.org \
--cc=lenbok@gmail.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).