vim + tmux + mouse can't click to place cursor
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
Recently I've lost the ability to click to select a specific cursor location or tab in vim sessions running under tmux. I can still use the mousewheel to scroll through a buffer, but the cursor position only changes when the current line scrolls off the screen.
Mouse operation is correct when running vim outside of tmux.
As far as I can tell, the only recent upgrades to the system have been unrelated -- the problem appeared after a recent reboot where the kernel and graphics driver were updated. This is an Arch system with the following stack:
i3wm
v4.14.1-2 updated last Octobersakura
terminal emulator v3.3.4-2 updated last April (problem also reproduces withurxvt
)tmux
v2.6-1 updated last Octobervim
8.0.1297 updated last month (problem reproducible with earlier versions as well)
.vimrc
settings verified active:
mouse=a
ttymouse=xterm2
.tmux.conf
settings verified active:
mouse on
default-terminal "screen-256color"
terminal-overrides[0] "xterm*:XT:Ms=\E]52;%p1%s;%p2%s\007:Cs=\E]12;%p1%s\007:Cr=\E]112\007:Ss=\E[%p1%d q:Se=\E[2 q"
terminal-overrides[1] "screen*:XT"
vim tmux
add a comment |Â
up vote
0
down vote
favorite
Recently I've lost the ability to click to select a specific cursor location or tab in vim sessions running under tmux. I can still use the mousewheel to scroll through a buffer, but the cursor position only changes when the current line scrolls off the screen.
Mouse operation is correct when running vim outside of tmux.
As far as I can tell, the only recent upgrades to the system have been unrelated -- the problem appeared after a recent reboot where the kernel and graphics driver were updated. This is an Arch system with the following stack:
i3wm
v4.14.1-2 updated last Octobersakura
terminal emulator v3.3.4-2 updated last April (problem also reproduces withurxvt
)tmux
v2.6-1 updated last Octobervim
8.0.1297 updated last month (problem reproducible with earlier versions as well)
.vimrc
settings verified active:
mouse=a
ttymouse=xterm2
.tmux.conf
settings verified active:
mouse on
default-terminal "screen-256color"
terminal-overrides[0] "xterm*:XT:Ms=\E]52;%p1%s;%p2%s\007:Cs=\E]12;%p1%s\007:Cr=\E]112\007:Ss=\E[%p1%d q:Se=\E[2 q"
terminal-overrides[1] "screen*:XT"
vim tmux
after another round of kernel update + reboot, the problem behavior has disappeared, so i suspect a bug and not a settings problem. voting to close.
â quixotic
Dec 15 '17 at 5:09
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Recently I've lost the ability to click to select a specific cursor location or tab in vim sessions running under tmux. I can still use the mousewheel to scroll through a buffer, but the cursor position only changes when the current line scrolls off the screen.
Mouse operation is correct when running vim outside of tmux.
As far as I can tell, the only recent upgrades to the system have been unrelated -- the problem appeared after a recent reboot where the kernel and graphics driver were updated. This is an Arch system with the following stack:
i3wm
v4.14.1-2 updated last Octobersakura
terminal emulator v3.3.4-2 updated last April (problem also reproduces withurxvt
)tmux
v2.6-1 updated last Octobervim
8.0.1297 updated last month (problem reproducible with earlier versions as well)
.vimrc
settings verified active:
mouse=a
ttymouse=xterm2
.tmux.conf
settings verified active:
mouse on
default-terminal "screen-256color"
terminal-overrides[0] "xterm*:XT:Ms=\E]52;%p1%s;%p2%s\007:Cs=\E]12;%p1%s\007:Cr=\E]112\007:Ss=\E[%p1%d q:Se=\E[2 q"
terminal-overrides[1] "screen*:XT"
vim tmux
Recently I've lost the ability to click to select a specific cursor location or tab in vim sessions running under tmux. I can still use the mousewheel to scroll through a buffer, but the cursor position only changes when the current line scrolls off the screen.
Mouse operation is correct when running vim outside of tmux.
As far as I can tell, the only recent upgrades to the system have been unrelated -- the problem appeared after a recent reboot where the kernel and graphics driver were updated. This is an Arch system with the following stack:
i3wm
v4.14.1-2 updated last Octobersakura
terminal emulator v3.3.4-2 updated last April (problem also reproduces withurxvt
)tmux
v2.6-1 updated last Octobervim
8.0.1297 updated last month (problem reproducible with earlier versions as well)
.vimrc
settings verified active:
mouse=a
ttymouse=xterm2
.tmux.conf
settings verified active:
mouse on
default-terminal "screen-256color"
terminal-overrides[0] "xterm*:XT:Ms=\E]52;%p1%s;%p2%s\007:Cs=\E]12;%p1%s\007:Cr=\E]112\007:Ss=\E[%p1%d q:Se=\E[2 q"
terminal-overrides[1] "screen*:XT"
vim tmux
asked Dec 13 '17 at 15:02
quixotic
570310
570310
after another round of kernel update + reboot, the problem behavior has disappeared, so i suspect a bug and not a settings problem. voting to close.
â quixotic
Dec 15 '17 at 5:09
add a comment |Â
after another round of kernel update + reboot, the problem behavior has disappeared, so i suspect a bug and not a settings problem. voting to close.
â quixotic
Dec 15 '17 at 5:09
after another round of kernel update + reboot, the problem behavior has disappeared, so i suspect a bug and not a settings problem. voting to close.
â quixotic
Dec 15 '17 at 5:09
after another round of kernel update + reboot, the problem behavior has disappeared, so i suspect a bug and not a settings problem. voting to close.
â quixotic
Dec 15 '17 at 5:09
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f410662%2fvim-tmux-mouse-cant-click-to-place-cursor%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
after another round of kernel update + reboot, the problem behavior has disappeared, so i suspect a bug and not a settings problem. voting to close.
â quixotic
Dec 15 '17 at 5:09