Open oschrenk opened 8 months ago
I'm trying to understand an error I am getting when working with :Lazy (in nvim 0.9.4) and vim-tmux-navigator.
Whenever Lazy is open and I am trying to navigate out of the window and jump to a neighboring tmux pane, I get
E11: Invalid in command-line window; <CR> executes, CTRL-C quits: wincm d k
It still works but it still shows an error. I believe it comes from here:
function! s:VimNavigate(direction) try execute 'wincmd ' . a:direction catch echohl ErrorMsg | echo 'E11: Invalid in command-line window; <CR> executes, CTRL-C quits: wincmd k' | echohl None endtry endfunction
When I comment out
echohl ErrorMsg | echo 'E11: Invalid in command-line window; <CR> executes, CTRL-C quits: wincmd k' | echohl None
I can still navigate panes without issues.
This is similar to
https://github.com/christoomey/vim-tmux-navigator/issues/67
I also get an error when trying to quit the window using :q but I am not sure if that is "caused" by the same issue, as in that case I see
:q
Error detected while processing WinLeave Autocommands for "*": E21: Cannot make changes, 'modifiable' is off
I'm trying to understand an error I am getting when working with :Lazy (in nvim 0.9.4) and vim-tmux-navigator.
Whenever Lazy is open and I am trying to navigate out of the window and jump to a neighboring tmux pane, I get
It still works but it still shows an error. I believe it comes from here:
When I comment out
I can still navigate panes without issues.
This is similar to
https://github.com/christoomey/vim-tmux-navigator/issues/67
I also get an error when trying to quit the window using
:q
but I am not sure if that is "caused" by the same issue, as in that case I see