101
29
In both zsh and bash, ctrl+arrows allows me to move the position I'm typing at by whole word, but this does not work in tmux, which is a problem as I'm currently launching it automatically every time I open a shell.
How can I fix this?
101
29
In both zsh and bash, ctrl+arrows allows me to move the position I'm typing at by whole word, but this does not work in tmux, which is a problem as I'm currently launching it automatically every time I open a shell.
How can I fix this?
133
Edit your ~/.tmux.conf
and add lines:
set-window-option -g xterm-keys on
If you don’t want to make it permanent just yet, do:
C-b :set-window-option xterm-keys on
Reload your config in tmux by doing:
C-b :source-file ~/.tmux.conf
More information here:
10
set-window-option -g xterm-keys on
Got me some of the way there and gave me Ctrl-Left/Right on the console, but it was still responding differently in vim.
Unbinding the keys didn't seem to help.
It turned out that at some point I had set my default terminal to screen (set-option -g default-terminal "screen"
in .tmux.conf
)
Changing this to the following gave me Ctrl-Left/Right in everything else:
set-option -g default-terminal "xterm-256color"
Hope that helps somebody.
1Except this breaks colors in vim, tig, and presumably a whole bunch of other stuff... – koniiiik – 2015-10-10T16:42:44.847
1
see also http://unix.stackexchange.com/a/1098/250 for an advice against setting TERM like that in tmux
– phunehehe – 2016-10-02T12:06:34.5573
For msys2/Cygwin/mintty:
Add below to ~/.inputrc
.
"\e[1;5C": forward-word # ctrl + right
"\e[1;5D": backward-word # ctrl + left
Reload would make tmux work correctly.
2
I'm not sure, but this might be because tmux
by default binds C-<up/down/left/right>
to shift the focus onto the pane above/below/left of/right of the currently focused pane. If you don't use panes often, you might not have noticed this feature. If this is what the problem is, you can unbind those keys by saying:
unbind C-Left
unbind C-Right
That might be enough on it's own, or you might need to manually bind them again to what you want them to do, via:
bind -n C-Left <the action you want>
bind -n C-Right <other action you want>
1It should be enough on it's own, if it isn't grabbed by tmux, it should pass onto the shell. – Rob – 2011-12-14T17:37:10.237
0
For me, the keys were not being bound correctly, because the system preferences in High Sierra were set to being used by Mission Control. Unchecking these then allowed the correct bindings to work in iTerm2 and Tmux
Unchecking all of the items referencing the control key, allowed the bindings to work properly
@AME close all tmux sessions then try again. – Nathan – 2015-09-07T06:13:25.843
1If reload config doesn't fix the problem (this is the case for me), try a new session. Maybe you need to kill the current session and create a new one. Another option to make it take effect in a pane (not a session) is C-b: respawn-pane -k – fstang – 2016-03-16T21:28:26.550
This worked for me, mostly. I wonder why it's not on by default? – inetknght – 2017-01-16T21:58:40.337
1Killing the session, or whatever
set-window-option -g xterm-keys on
still doesn't do anything in my case. – noraj – 2017-11-12T23:57:57.020press
C-b
thenkill-server
ortmux kill-server
before testing the result – Fabrizio Bertoglio – 2020-01-24T09:56:56.1772Strange: This works for me only if I reload the ~/.tmux.conf file from tmux or set the action in the :-prompt of tmux, not initially when I open tmux. Any ideas what might be the problem there? – AME – 2013-11-28T18:06:12.107