unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ergus <spacibba@aol.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Juri Linkov <juri@linkov.net>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: xterm [menu] key definition
Date: Wed, 25 Aug 2021 10:58:10 +0200	[thread overview]
Message-ID: <20210825085810.ryimt5tsanjfqt4n@Ergus> (raw)
In-Reply-To: <jwvv93ubcbl.fsf-monnier+emacs@gnu.org>

On Tue, Aug 24, 2021 at 10:53:55PM -0400, Stefan Monnier wrote:
>> Please give a look to my last email to Eli. I attached an answer from
>> the xterm maintainer respecting to that. That included a xev output and
>> his comment about this.
>[...]
>> xterm does not map either [print] or [menu] in terminfo but maps
>> kf16=\E[29~ (that's why urxvt mapped S-<f6> == <f16> == [menu] according
>> to their convention)
>
>So, IIUC he's saying that xterm emits `\E[29~` not for `Print` nor for
>`Menu` but for `F16`, right?  So maybe we should have
>
>    (define-key map "\e[29~" [f16])
>
>and then remap `f16` to `menu` maybe even via `S-f6`, but we already
>have a remapping of `f16` to `S-f4`, so it looks like a big pile of mess.
>
in xterm normally `f16` == `S-f4` because the last fkey is 12 not
10. The one with the `wrong` (or less standard) convention here is
urxvt. So our current remapping is fine in this case

>> The real question is why emacs mapped \E[29~ to [print] in xterm;
>
>This dates back to:
>
>    commit 92abb02b9b65b95807fd8fdccad10feed0dd3a96
>    Author: Karl Heuer <kwzh@gnu.org>
>    Date:   Fri Jun 9 02:31:33 1995 +0000
>
>        Initial revision
>
>so maybe some kind of xterms back then did that?
>
>FWIW, the f16 => S-f4 mapping dates back to:
>
>    commit 35b1b8abe3d3833ecb4b4cee75b7340ffb707d65
>    Author: Dan Nicolaescu <dann@ics.uci.edu>
>    Date:   Tue Apr 26 05:56:22 2005 +0000
>
>        * NEWS: Mention xterm key bindings.
>
>        * term/xterm.el (function-key-map): Fix strings for
>        {C,S,A,C-S}-f[1-4]. Use substitute-key-definition to bind
>        {C,S,A,C-S}-{f1-f12}.
>
And it is actually fine ;)

>Do you have a "menu" key which emits the `Menu` X11 event and for which
>your terminal emits `\E[29~`?
Indeed. I have the same behavior the xterm maintainer described for his
system.

>If so, which terminal is that (details
>like the version may be relevant and maybe the OS or environment)?
>
>
>        Stefan
>
xterm: 368 (but very old versions have the same behavior), OS: Debian,
Arch Linux and Open Suse different versions.



  reply	other threads:[~2021-08-25  8:58 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210819024728.kgnf6jmpakqdto4p.ref@Ergus>
2021-08-19  2:47 ` xterm [menu] key definition Ergus
2021-08-23 17:53   ` Ergus
2021-08-24  6:37   ` Juri Linkov
2021-08-24  8:19     ` Ergus
2021-08-24  8:34       ` tomas
2021-08-24  9:17         ` Ergus
2021-08-24 10:03           ` Andreas Schwab
2021-08-24 11:00           ` tomas
2021-08-24 15:30             ` Ergus
2021-08-25  7:06               ` tomas
2021-08-25  9:32                 ` Ergus
2021-08-25 10:47                   ` tomas
2021-08-25 11:31                     ` Ergus
2021-08-26  5:47                     ` chad
2021-08-26  7:14                       ` tomas
2021-08-26  8:16                       ` Andreas Schwab
2021-08-24  8:34       ` Andreas Schwab
2021-08-24  9:07         ` Ergus
2021-08-24 22:05       ` Stefan Monnier
2021-08-25  6:38         ` tomas
2021-08-25  9:04           ` Ergus
2021-08-24 16:40     ` Ergus via Emacs development discussions.
2021-08-24 17:28       ` Eli Zaretskii
2021-08-24 18:09         ` Juri Linkov
2021-08-24 20:23         ` Ergus
2021-08-25 11:27           ` Eli Zaretskii
2021-08-25 11:53             ` Ergus
2021-08-24 22:16       ` Stefan Monnier
2021-08-24 23:20         ` Ergus
2021-08-25  2:53           ` Stefan Monnier
2021-08-25  8:58             ` Ergus [this message]
2021-08-25 14:13               ` Stefan Monnier
2021-08-25 11:34             ` Eli Zaretskii
2021-08-25 22:41               ` Stefan Monnier
2021-08-26  6:55                 ` Eli Zaretskii
2021-08-26  7:17                   ` Ergus
2021-08-26  7:23                     ` Eli Zaretskii
2021-08-26 12:52                   ` Ergus
2021-08-26 13:48                     ` Eli Zaretskii
2021-08-26 13:59                   ` Stefan Monnier
2021-08-26 14:51                     ` Andreas Schwab
2021-08-26 15:52                     ` Eli Zaretskii
2021-08-25  7:10           ` tomas
2021-08-25  8:02           ` Andreas Schwab
2021-08-25  6:36         ` Yuri Khan
2021-08-25  7:17           ` tomas
2021-08-25  9:00           ` Ergus
2021-08-25 14:01         ` Olaf Rogalsky
     [not found]   ` <87k0kcovp4.fsf@no.workgroup>
2021-08-25 12:09     ` Gregor Zattler

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=20210825085810.ryimt5tsanjfqt4n@Ergus \
    --to=spacibba@aol.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    --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).