Hi,
I noticed that some work was done a few hours ago on tmux to "Detect
iTerm2 and enable DECSLRM." [1] This appears to have broken tmux mouse
support in tmux running on OpenBSD-current [2] when connecting over SSH
from a macOS host running iTerm2.
My ~/.tmux.conf file looks like
set-option -g mouse on
set-option -g prefix C-a
bind-key C-a send-prefix
and my iTerm2 3.3.7 on macOS is set up to report a terminal type of
"xterm", no ENQ answer back string, and has "Enable mouse reporting" and
"Report mouse wheel events" enabled.
By "broken", I mean that while mouse-clicks etc. seems to send
*something* to tmux, tmux apperas to have issues interpreting what to
do. Clicking in an inactive pane may, for example, move the cursor to a
different location in nvi running in the active pane.
Running hexdump -C, clicking once, and pressing return followed by
Ctrl+D produces
% hexdump -C
^[[<0;131;32M^[[<0;131;32m
00000000 1b 5b 3c 30 3b 31 33 31 3b 33 32 4d 1b 5b 3c 30
|.[<0;131;32M.[<0|
00000010 3b 31 33 31 3b 33 32 6d 0a |;131;32m.|
00000019
[1]
https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/tmux/tty-keys.c.diff?r1=1.118&r2=1.119&sortby=date&f=h
[2] OpenBSD pooh 6.6 GENERIC.MP#600 amd64
--
Andreas (Kusalananda) Kähäri
SciLifeLab, NBIS, ICM
Uppsala University, Sweden
