-
Notifications
You must be signed in to change notification settings - Fork 315
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
<C-h> and <C-l> broken inside netrw(neovim). is there any way to fix? #379
Comments
Ask-786
changed the title
<C-h> and <C-l> inside netrw(neovim). is there any way to fix?
<C-h> and <C-l> broken inside netrw(neovim). is there any way to fix?
Mar 27, 2024
Seems like this is caused by netrw overriding the let g:Netrw_UserMaps = [["<C-l>","<C-U>TmuxNavigateRight<cr>"]] Or in neovim: vim.g.Netrw_UserMaps = { { "<C-l>", "<C-U>TmuxNavigateRight<cr>" } } |
Closed
nfischer
added a commit
to nfischer/vim-tmux-navigator
that referenced
this issue
May 25, 2024
This adds a workaround for the netrw keymapping conflict for ctrl-l by setting the `g:Netrw_UserMaps` list. To limit the impact to users, this will leave the list alone if the user has already set the variable and instead gives a warning to prompt the user about the issue. This mapping workaround can be disabled by setting either `g:tmux_navigator_no_mappings` or `g:tmux_navigator_disable_netrw_workaround`. Fixes christoomey#189, Fixes christoomey#251, Fixes christoomey#379
christoomey
pushed a commit
that referenced
this issue
May 26, 2024
This adds a workaround for the netrw keymapping conflict for ctrl-l by setting the `g:Netrw_UserMaps` list. To limit the impact to users, this will leave the list alone if the user has already set the variable and instead gives a warning to prompt the user about the issue. This mapping workaround can be disabled by setting either `g:tmux_navigator_no_mappings` or `g:tmux_navigator_disable_netrw_workaround`. Fixes #189, Fixes #251, Fixes #379
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: