Background
I use Byobu with Tmux backend.1
Problem
- Moving across panes is inconvenient.
- If I have a Vim vertical/horizontal split in a Tmux pane, I need to use two different sets of key bindings to navigate the adjacent panes.
- In the copy mode, it’s great that most of the key bindings follow
from those of Vim, but not the most important two:
- start selection
- copy
Solution
I find two articles on Giant Robots very useful.
Therefore, I followed the steps in the first blog post, and installed Vim Tmux Navigator.
Another problem
After the installation of the Vim plugin, I got another problem while
editing my VIMRC: The {Down-Mapping}
didn’t work.
Vim-$\rm \LaTeX$ should know the reason. I found an
article describing a similar problem.2 However, I wouldn’t
like to change ~/.vim/bundle/vim-latex/plugin/imaps.vim
, so I got
stuck at this point for hours. I tried to substitute {Down-Mapping}
with <C-a>j
in VIMRC, but it didn’t work.
Lessons Learnt
-
Accept simple ways to do things
Even though I can’t set
{Down-Mapping}
to<C-j>
, the Vim editor command:TmuxNavigateDown
isn’t so hard to type. I failed to realise that typing:tm<Tab>
will do, and wasted time on that. Now I accept the use of two different sets of keystrokes for switching to the Tmux pane/Vim buffer below. We can look at this problem from another angle. -
Store a list of windows in a file
A sample file can be found on Super User.3 I found that if I had run Byobu before, a session
0
would also be created on top oftmuxs
. To avoid this problem, remove the first line in the sample window list and typebyobu attach -t 0
starting from the second time of opening Byobu.
-
See Use Tmux for Previewing Posts in this blog for details. ↩
-
See Key mapping collision between vim-navigation and vim-latex by Chris Choy for details. ↩
-
See Proper Format for Byobu’s windows.tmux? on Super User. ↩