-
Notifications
You must be signed in to change notification settings - Fork 336
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Not an editor command: ^UTmuxNavigateRight" after changing keys table in lazy.nvim #397
Comments
Hmm, I'm not certain as I'm not yet on neovim / lazy.nvim, but I think the |
Thanks so much for getting back to me so quickly! That did indeed seem to solve the problem for me! Interesting that the I also tried the original I'm curious -- what's the purpose of the Anyway, I really appreciate the help! |
I had the same issue. After deleting the it started working well. I am also curious about the purpose of prepending . I appreciate the nice plugin! Mine is for lazy.nvim + colemak users {
"christoomey/vim-tmux-navigator",
cmd = {
"TmuxNavigateLeft",
"TmuxNavigateDown",
"TmuxNavigateUp",
"TmuxNavigateRight",
"TmuxNavigatePrevious",
},
keys = {
{ "<c-h>", "<cmd>TmuxNavigateLeft<cr>" },
{ "<c-n>", "<cmd>TmuxNavigateDown<cr>" },
{ "<c-e>", "<cmd>TmuxNavigateUp<cr>" },
{ "<c-i>", "<cmd>TmuxNavigateRight<cr>" },
{ "<c-\\>", "<cmd>TmuxNavigatePrevious<cr>" },
},
}, |
I have the same issue in NVChad, had to drop the following into my mappings.lua file -- Disable the existing key mappings for tmux navigation map("n", "", "TmuxNavigateDown") |
Hello! I just got turned onto this plugin, and the default configuration seems to work great!
However, I already have my
<C-h/j/k/l>
keys bound, so I wanted to switch my key bindings on the neovim side to the standard<c-w>h/j/k/l
that I've been using.When I try to set this in lazy.nvim's keys table, I receive the "E492: Not an editor command: ^UTmuxNavigateRight" error whenever I try to navigate (the error changes for right/left/up/down).
My config looks like this:
The text was updated successfully, but these errors were encountered: