vim + tmux + mouse can't click to place cursor

The name of the pictureThe name of the pictureThe name of the pictureClash 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 October


  • sakura terminal emulator v3.3.4-2 updated last April (problem also reproduces with urxvt)


  • tmux v2.6-1 updated last October


  • vim 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"






share|improve this question




















  • 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















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 October


  • sakura terminal emulator v3.3.4-2 updated last April (problem also reproduces with urxvt)


  • tmux v2.6-1 updated last October


  • vim 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"






share|improve this question




















  • 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













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 October


  • sakura terminal emulator v3.3.4-2 updated last April (problem also reproduces with urxvt)


  • tmux v2.6-1 updated last October


  • vim 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"






share|improve this question












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 October


  • sakura terminal emulator v3.3.4-2 updated last April (problem also reproduces with urxvt)


  • tmux v2.6-1 updated last October


  • vim 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"








share|improve this question











share|improve this question




share|improve this question










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

















  • 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
















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















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



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes










 

draft saved


draft discarded


























 


draft saved


draft discarded














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













































































Popular posts from this blog

How to check contact read email or not when send email to Individual?

Displaying single band from multi-band raster using QGIS

How many registers does an x86_64 CPU actually have?