That’s because vim is doing strange things that neovim does not do. All the details are in the issue linked by the FAQ.
All you need to do is execute the two commands listed and it should work fine. > On Sep 10, 2016, at 6:53 AM, Luis Henriquez-Perez > <luishenriquezpe...@gmail.com> wrote: > > What's very strange is that the mapping works correctly in regular Vim. > > On Saturday, September 10, 2016 at 6:44:51 AM UTC-4, Luis Henriquez-Perez > wrote: > In neovim I want to map keys in normal mode so that switching between > different buffers is faster. I did this with "nnoremap <C-h> <C-W>h" for > h,j,k,l. All of these mappings work except for the one to <C-h>. I used > ":verbose map <c-h>" and it returned that <c-h> was mapped correctly (to > <C-W>h). I'm almost certain that the nvim key binding is being "intercepted" > by a key binding from either my mac or one of the apps in it, but I have no > idea how to find out for sure. > > How do I figure out where this interception is coming from? > > -- > You received this message because you are subscribed to the Google Groups > "neovim" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to neovim+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "neovim" group. To unsubscribe from this group and stop receiving emails from it, send an email to neovim+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
