-
-
Notifications
You must be signed in to change notification settings - Fork 11.4k
tmux 2.1 update breaks keyboard mappings #45413
Comments
I know some defaults were changed in this release, so this might not be Homebrew-specific. Can you check if this happens with a tmux built outside Homebrew? |
I don't know if this is an appropriate place to offer alternatives, so please forgive me if this is a faux pas. There's a setting in iTerm which allows the option key to be used as Meta. You can choose either Meta or Esc+ (they act mostly the same). Then in tmux, you can use
|
@dunn: I haven't had time to build tmux from source, but when I manually copied the old version (opt/homebrew/Cellar/tmux/2.0) from another OS X machine and launched it directly from the bin/ folder, the issue went away. That's with an up to date tmux with all other packages upgraded to current latest versions, so seems like a pretty strong indication that the issue is specific to the tmux package. |
See tmux/tmux#159. Running |
If the developers can be convinced to change the default configuration, we'll be happy to backport the change! |
Agreed 👍 |
Thanks @tt. Adding |
Hooray! |
Thanks so much, just invested another 4 hours into my dotfiles just to have the new keybindings not working on my other machine. |
This is an upstream issue. We'll consider a PR to improve our configuration but it's not Homebrew's bug so closing. |
I use iTerm + tmux, with "send hex code" keyboard shortcuts mapped to switch prev/next pane.
eg. I have Option+h mapped to send "0x01 0x70" and Option+l mapped to "0x01 0x6E". This allows rapid switching between panes with hjkl direction keys.
Since updating to tmux 2.1, this is partially broken. Hitting Option+h the first time prints "p" into the console. Hitting it a second time successfully fires the sequence, triggering pane switching. Ditto for all my other mappings.
I can still successfully use this mappings when SSH'ed into other remote servers (using iTerm locally and tmux remotely), which leads me to conclude that the issue is with my local Mac's tmux version.
The text was updated successfully, but these errors were encountered: