GNU bug report logs - #60077
29.0.60; Is xterm modifyOtherKeys support broken?

Previous Next

Package: emacs;

Reported by: Len Trigg <lenbok <at> gmail.com>

Date: Wed, 14 Dec 2022 21:50:02 UTC

Severity: normal

Found in version 29.0.60

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Len Trigg <lenbok <at> gmail.com>
Cc: 60077 <at> debbugs.gnu.org
Subject: bug#60077: 29.0.60; Is xterm modifyOtherKeys support broken?
Date: Thu, 15 Dec 2022 11:10:39 +0200
> From: Len Trigg <lenbok <at> gmail.com>
> Date: Thu, 15 Dec 2022 21:57:00 +1300
> Cc: 60077 <at> debbugs.gnu.org
> 
> On Thu, 15 Dec 2022 at 21:38, Len Trigg <lenbok <at> 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.




This bug report was last modified 2 years and 153 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.