hine and can verify that the functionality is
> back.
>
> I am talking about the extended function keys. In 1.8 I can do
> "send-keys F13" and get the appropriate F13 key sequence to be
> interpreted by my terminal. In v 1.9 it simply sends the literal
> string "F13". I
talking about the extended function keys. In 1.8 I can do
"send-keys F13" and get the appropriate F13 key sequence to be
interpreted by my terminal. In v 1.9 it simply sends the literal string
"F13". I am using identical an identical tmux.conf for both scenarios.
Is this a bug or
On 2014-07-15 22:00 -0400, Bryan Mills wrote:
> With tmux, the escape keys aren't recognized. Presumably something in
> the screen-256color termcap is off.
$ infocmp screen-256color | grep kf
kdch1=\E[3~, kend=\E[4~, kf1=\EOP, kf10=\E[21~,
kf11=\E[23~, kf12=\E[24~, kf2=\EO
Doesn't work, with xterm-keys on or off.
Without tmux in the middle, xterm with emacs works all the way up
through F24 (as high as the USB HID tables go).
With tmux, the escape keys aren't recognized. Presumably something in
the screen-256color termcap is off.
On Tue, Jul 15, 2014 at 12:36 AM
Looks fine to me, although tmux only supports up to F20.
If you turn on the xterm-keys option you should get the xterm escape
sequences instead of the normal tmux ones.
On Tue, Jul 15, 2014 at 12:04:18AM -0400, Bryan Mills wrote:
> I've been experimenting with alternate keyboards lately, and I'v
I've been experimenting with alternate keyboards lately, and I've got
a USB HID device that generates lesser-used function key codes
(F13-F24).
I managed to get xterm configured decently enough to forward them to
emacs, so everything seems to be plumbed properly...
Only, if I throw tmux in the mi
