all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: lenbok@gmail.com
Cc: 60077-done@debbugs.gnu.org
Subject: bug#60077: 29.0.60; Is xterm modifyOtherKeys support broken?
Date: Fri, 16 Dec 2022 18:04:09 +0200	[thread overview]
Message-ID: <835yebjpxi.fsf@gnu.org> (raw)
In-Reply-To: <83r0wzkfgx.fsf@gnu.org> (message from Eli Zaretskii on Fri, 16 Dec 2022 08:52:30 +0200)

> Cc: dann@ics.uci.edu, 60077@debbugs.gnu.org
> Date: Fri, 16 Dec 2022 08:52:30 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> 
> > From: Len Trigg <lenbok@gmail.com>
> > Date: Fri, 16 Dec 2022 08:48:54 +1300
> > Cc: 60077@debbugs.gnu.org, dann@ics.uci.edu
> > 
> > On Thu, 15 Dec 2022 at 22:10, Eli Zaretskii <eliz@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.
> 
> OK, will install that soon.

Now done on the emacs-29 branch, and closing the bug.

Thanks.





  parent reply	other threads:[~2022-12-16 16:04 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=835yebjpxi.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=60077-done@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.