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

Previous Next

Full log

Message #23 received at 60077 <at> debbugs.gnu.org (full text, mbox):

From: Len Trigg <lenbok <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: dann <at> ics.uci.edu, 60077 <at> debbugs.gnu.org
Subject: Re: bug#60077: 29.0.60; Is xterm modifyOtherKeys support broken?
Date: Fri, 16 Dec 2022 08:48:54 +1300

[Message part 1 (text/plain, inline)]

On Thu, 15 Dec 2022 at 22:10, Eli Zaretskii <eliz <at> gnu.org> wrote:

> > 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.
>

I tried this out and it does fix the issue for me. BTW, have you tried to
replicate the issue yourself?


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.
>

I suppose so, I'm just a little wary of fixing like this without
understanding why it only seems to be an issue now or whether other guards
are needed. For example, the commit log for this area shows Dan Nicolaescu
adding more bindings in c0658ad46e4928ecdf6a14904073dc8a2fcfe862 and also
bumping the xterm version number that is checked against, so he is probably
knowledgeable about how this works. (I've tried to add him to the CC list
using the email address in that commit)

Cheers,
Len.

[Message part 2 (text/html, inline)]

Previous Next

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