Re: xterm [menu] key definition

[Ergus]

On Wed, Aug 25, 2021 at 02:27:21PM +0300, Eli Zaretskii wrote:
> > Date: Tue, 24 Aug 2021 22:23:40 +0200
> > From: Ergus <spacibba@aol.com>
> > Cc: juri@linkov.net, monnier@iro.umontreal.ca, emacs-devel@gnu.org
> >
> > I am not saying the current code is wrong. Just that the so called
> > [print] key does not exist while the same key is seen as [menu] in gui.
>
> We need evidence for that, and we need evidence that would explain why
> xterm.el does have a translation for that key.
This was my very first question on this: why Print. And why I started
this thread. In the worst case we shouldn't have mapped the escape no
anything or in the best it should be bound to <f16> for what I have
learned here.

> > I already wrote to Thomas Dickey (xterm maintainer) some days ago about
> > this:
>
> AFAIU, Thomas just says that he doesn't know of any standard xterm
> assignment to the Menu key.  I already knew that, because I looked
> into the xterm sequences documentation when you first reported the
> issue.  So what Thomas wrote doesn't tell me anything new.
The maps are there as mentioned before by Yuri:

https://github.com/Maximus5/xterm/blob/master/src/input.c#L1460

> > The other change I propose is the S-<f6> instead of S-<f10> and for that
> > we have all the evidence that urxvt binds the same escape sequence to
> > S-<f6> (since we do:
> >
> > lisp/term/rxvt.el:67:    (define-key map "\e[29~" [S-f6])
>
> I don't think using S-F6 for this is a good idea.  F10 is our key for
> menus, so S-F10 sounds a lot better.
From the code it looks like [menu] is an alias for <f16>. rxvt
convention makes <f 10+X> = S-<fX>. xterm used a similar approach but
with 12 instead of 10; now it is more complete and with many more
bindings emacs does not support for backward compatibility... (like
C-S-letter for example)

> > Otherwise we will need to request to all the compatible terminals around
> > to update their terminfo.. a very long process that will delay for years
> > until all the systems in all the servers will be updated.
>
> I don't understand why would we need to request anything.  If this is
> for the Print key, then since it seems that no keyboard has it, we are
> good.
Not for the print; but for the menu. When I wrote this I didn't know it
was generally an alias for <f16>.