Re: xterm [menu] key definition

[Ergus <spacibba@aol.com>]

On Tue, Aug 24, 2021 at 06:16:01PM -0400, Stefan Monnier wrote:
>> -    (define-key map "\e[29~" [print])
>> +    (define-key map "\e[29~" [menu])
>
>This might be right, but we need some more concrete evidence that indeed
>`xterm` maps `Menu` to `\e[29~` by default and/or that `Print` is not
>mapped to `\e[29~` by default, or something like that.
>
>That info should be available in `xterm`s source code or something like
>that (I hoped that it would be visible in the `app-defaults/XTerm` file
>but no).
>
>
>        Stefan
>
Hi Stefan:

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)

In xterm that mapping (S-<fX> == <f10+X>) depends of the variable
modifyFunctionKeys. But in any case this does not affect the [menu] key
that is not translated.

The real question is why emacs mapped \E[29~ to [print] in xterm;
because the Print key is normally intercepted by the windows manager.

Best,
Ergus