[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: xterm [menu] key definition

From: Ergus
Subject: Re: xterm [menu] key definition
Date: Mon, 23 Aug 2021 19:53:17 +0200


I will insist on this. The change is very simple, but I don't know if
there will be any consequence.

On Thu, Aug 19, 2021 at 04:47:28AM +0200, Ergus wrote:

Due to the recent context-menu feature I was trying to bind the [menu]
key to the context-menu and just noticed that on xterm emacs detects the
menu key as [print]; so it does not trigger the execute-extended-command
(which is bound to <execute>, <menu> and M-x by default).

cat+xterm shows that the menu key sends "\e[29~"

Grepping in the term directory there is.

lk201.el:35:    (define-key map "\e[29~" [menu])
rxvt.el:67:    (define-key map "\e[29~" [S-f6])
xterm.el:353:    (define-key map "\e[29~" [print])

And xev says that "\e[29~" is actually [Menu] and detects it properly so
there is a mismatch here.

I don't know if this is an issue or some design choice made long time
ago (in 2007), but it makes that the menu button does not behave the
same in xterm, gui or rxvt. The user can go around this binding [Print]
to whatever, but if there is not a reason, then maybe it worth doing.

(define-key map "\e[29~" [menu]) in xterm.el too?

I don't actually know about any keyboard with a print button... But I
suppose there should be some. If someone has it; please could you check
with xev and cat+xterm what it sends?

Thanks in advance,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]