- use a list instead of single string
- add s:GetTmuxCommand to be used later when not using `system()` only
- remove `:silent` when calling tmux from `s:TmuxAwareNavigate`: it
should not be necessary and is bad practice to use `:silent`
unnecessarily. It was added in b068a04 with no explanation.
Why
---
https://github.com/christoomey/vim-tmux-navigator/pull/181 was
introduced to fix an issues with the TPM install script not running
cleanly. This was due to the `C-\` key binding not being properly
escaped in the final line of the script.
In the process of fixing this in #181, it looks like we took it a bit
overboard and escaped _all_ `C-\` sequences. In the end, the others
should not be escaped, so this was causing issues for users not
configuring via TPM script.
This change
-----------
This change reverts all of the `C-\` escaping outside of the TPM script.
Users have requested the ability to disable navigation while the Vim
tmux pane is zoomed, to prevent accidentally unzooming the pane when
navigating past the edges.
This change adds an option to prevent using tmux navigation when the Vim
pane is zoomed, and requiring an explicit unzooming of the tmux pane
before the plugin resumes its magic.
Summary: Added a new behaviour to tmux_navigator_save_on_switch which, when
set, causes all open and changed buffers to be written when navigating away
from a vim session.
Summary: Fixes#142. An issue existed where opening vim without a file
path and then navigating away (with autosave turned on) resulted in an
error being thrown. Now, this error is caught and consumed and not
propagated to the user.
Test Plan:
1) Started up a vim instance without a file path.
2) Created a second tmux pane.
3) navigated to tmux pane with vim
4) entered insert mode and wrote some gibberish
5) navigated away from the tmux pane containing the vim instance
6) no error message was shown to me
https://github.com/christoomey/vim-tmux-navigator/issues/71
This addition to the readme should point users to possible solutions for
their kbs/terminfo/libtermkey woes when using Neovim, which has been an
ongoing issue for users and is not directly related to
vim-tmux-navigator.
Close#71.
Some distributions ship 'vim' without xterm_clipboard support. A separate
package vim-x11 or similar then ships another binary 'vimx' with that
support.
To support vim-tmux-navigator with such a binary name, adapt the pattern
check to allow an optional 'x'.
This makes use of an inlined variable in the `.tmux.conf` which removes
the duplication of the pattern, and `if-shell` in place of the inlined
command sequence previously used through `run-shell`.
Initially hoped to use via shell pattern matching, but that lost the
case-insensitivity that `grep -iqE` had.
Incorporates feedback from:
Suggest tmux if-shell instead of run-shell - #31
Less cluttered run-shell bindings - #44
Added suggestion for faster commands in zsh - #40
The suggested regex was filtering out the `nvim` editor name for neovim. I
had initially thought that it was some kind of key binding problem in neovim,
but making this change allows pane/split switching in either vim or neovim.
This pull request edits the .tmux.conf provided in the README to grep
-iqE '(^|\/)g?(view|vim?)(diff)?$'.
This change makes it so that the same configuration will work for either
vi vim gvim view or gview setups.
