tmux interfering with vim mouse commands, depending on pointer location
up vote
0
down vote
favorite
For several years, I've been running an environment that very smoothly uses vim inside of tmux. But they've recently started fighting with one another, and I don't understand why.
If the mouse pointer is either too far to the right or (sometimes) too far down the screen, mouse commands somehow get garbled. Attempting to click tabs on the right side at the top of vim produces exclamation points in the gutter. Scrolling up or down will, if I'm too far to the right, produce weirdly random character output.
If I run vim outside of a tmux session it works fine, so it has to be the interaction between the two that's causing an issue.
I do have these options set in my .tmux.conf:
set -g default-terminal "screen-256color"
set-window-option -g xterm-keys on
set-option -g mode-mouse on
Anybody have any ideas about what's going on or how I can fix it?
FWIW, I'm running iTerm2 on Mac, with the tmux integration that treats each window as its own tab. No idea if that's a possible contributing factor.
vim tmux
asked Nov 14 at 20:17
BlairHippo
1032213
add a comment |
up vote
0
down vote
favorite
For several years, I've been running an environment that very smoothly uses vim inside of tmux. But they've recently started fighting with one another, and I don't understand why.
If the mouse pointer is either too far to the right or (sometimes) too far down the screen, mouse commands somehow get garbled. Attempting to click tabs on the right side at the top of vim produces exclamation points in the gutter. Scrolling up or down will, if I'm too far to the right, produce weirdly random character output.
If I run vim outside of a tmux session it works fine, so it has to be the interaction between the two that's causing an issue.
I do have these options set in my .tmux.conf:
set -g default-terminal "screen-256color"
set-window-option -g xterm-keys on
set-option -g mode-mouse on
Anybody have any ideas about what's going on or how I can fix it?
FWIW, I'm running iTerm2 on Mac, with the tmux integration that treats each window as its own tab. No idea if that's a possible contributing factor.
vim tmux
asked Nov 14 at 20:17
BlairHippo
1032213
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
For several years, I've been running an environment that very smoothly uses vim inside of tmux. But they've recently started fighting with one another, and I don't understand why.
If the mouse pointer is either too far to the right or (sometimes) too far down the screen, mouse commands somehow get garbled. Attempting to click tabs on the right side at the top of vim produces exclamation points in the gutter. Scrolling up or down will, if I'm too far to the right, produce weirdly random character output.
If I run vim outside of a tmux session it works fine, so it has to be the interaction between the two that's causing an issue.
I do have these options set in my .tmux.conf:
set -g default-terminal "screen-256color"
set-window-option -g xterm-keys on
set-option -g mode-mouse on
Anybody have any ideas about what's going on or how I can fix it?
FWIW, I'm running iTerm2 on Mac, with the tmux integration that treats each window as its own tab. No idea if that's a possible contributing factor.
vim tmux
asked Nov 14 at 20:17
BlairHippo
1032213
For several years, I've been running an environment that very smoothly uses vim inside of tmux. But they've recently started fighting with one another, and I don't understand why.
If the mouse pointer is either too far to the right or (sometimes) too far down the screen, mouse commands somehow get garbled. Attempting to click tabs on the right side at the top of vim produces exclamation points in the gutter. Scrolling up or down will, if I'm too far to the right, produce weirdly random character output.
If I run vim outside of a tmux session it works fine, so it has to be the interaction between the two that's causing an issue.
I do have these options set in my .tmux.conf:
set -g default-terminal "screen-256color"
set-window-option -g xterm-keys on
set-option -g mode-mouse on
Anybody have any ideas about what's going on or how I can fix it?
FWIW, I'm running iTerm2 on Mac, with the tmux integration that treats each window as its own tab. No idea if that's a possible contributing factor.
vim tmux
vim tmux
asked Nov 14 at 20:17
BlairHippo
1032213
asked Nov 14 at 20:17
BlairHippo
1032213
asked Nov 14 at 20:17
BlairHippo
1032213
asked Nov 14 at 20:17
BlairHippo
1032213
asked Nov 14 at 20:17
BlairHippo
1032213
1032213
add a comment |
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1375442%2ftmux-interfering-with-vim-mouse-commands-depending-on-pointer-location%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
