Problems with ctrl-h in neovim

Question

Problems with ctrl-h in neovim

pwntester opened this issue 9 years ago · comments

Hi, First of all, this is a great addition to my workfow, thanks!

I know, this is probably a problem with neovim, but control-h does not work there using standard configuration. Is there anything that can be done with any mapping settings?

Thanks
A

Chris Toomey · Answer 1 · Thu Apr 16 2015 20:40:22 GMT+0800 (China Standard Time)

Hi @pwntester, glad you've found it useful!

I'm not a neovim user myself, but my guess is that the issue lies there. You can confirm that the mapping is configured properly by running:

verbose nmap <C-h>

And it should mention tmux navigator.

Also, I think #61 is about the same issue and might contain a fix.

Alvaro Muñoz · Answer 2 · Thu Apr 16 2015 23:20:16 GMT+0800 (China Standard Time)

Thanks!

infocmp $TERM | sed 's/kbs=^[hH]/kbs=\\177/' > $TERM.ti
tic $TERM.ti

That worked for me, thanks!!!

Chris Toomey · Answer 3 · Thu Apr 16 2015 23:23:43 GMT+0800 (China Standard Time)

Glad to hear it. Closing this now as your issue seems resolved, but please feel free to reopen or comment if needed.

Alex LaFroscia · Answer 4 · Fri Apr 24 2015 14:43:35 GMT+0800 (China Standard Time)

I'm seeing this issue too, everything works except for <C-H> despite the fact that :TmuxNavigatorLeft is fine. Pasting the snippet above does fix the problem, but not knowing what it does, I feel a little weird using it.

Edit: Not sure why, but even the above fix isn't working for me anymore

Dominique Luna · Answer 5 · Fri Jun 05 2015 03:16:00 GMT+0800 (China Standard Time)

I think might be a problem with the bash shell and the regex.

I had

set shell=/bin/bash

That shell was 3.2

I changed it to

set shell=/usr/local/bin/bash

This one is 4.3

and the issue seems to be gone.

Jon Kinney · Answer 6 · Wed Jun 10 2015 01:19:06 GMT+0800 (China Standard Time)

Pasting the fix @pwntester mentioned and using a brew based 4.3 version of bash seems to have fixed this issue for me for neovim when not run inside of tmux. But I still can't C-h in vim when using tmux. It'll navigate the tmux splits with C-h just fine, but when it gets to vim, then C-h is just a noop.

Update: I checked echo $TERM and it was set to screen-256color even though I had it set in iterm2 as xterm-256color. I added export TERM='xterm-256color' to my ~/.zshrc and then C-h worked.

Grimmjaw · Answer 7 · Fri Jun 26 2015 12:17:45 GMT+0800 (China Standard Time)

Was having the same issue with everything but Ctrl+h working in Neovim and Tmux.

infocmp $TERM | sed 's/kbs=^[hH]/kbs=\177/' > $TERM.ti
tic $TERM.ti

No idea what that snippet does, but after running it in zsh, Ctrl+h now works

Felix Jung · Answer 8 · Thu Jul 30 2015 20:44:22 GMT+0800 (China Standard Time)

Hm I can't run tic $TERM.ti to verify the fix. Otherwise I'm also having this problem. Using homebrew zsh.

Seth Messer · Answer 9 · Tue Aug 25 2015 10:06:59 GMT+0800 (China Standard Time)

also having the issue @felixjung / @christoomey.
osx 10.10.5
homebrew
tmux
zsh
neovim (terminal brew vim works fine)
i've tried with both xterm-256color and screen-256color

output of verbose nmap <C-h>:

<C-H>       * :TmuxNavigateLeft<CR>
Last set from ~/.nvimrc

UPDATE: nevermind, I just followed the barrage of solutions over at neovim/neovim#2048;

seems to all work again.

Dave Yarwood · Answer 10 · Sat Oct 10 2015 02:41:27 GMT+0800 (China Standard Time)

I'm experiencing what I think may be a strange variation on this problem... for me, <C-h> is being captured by Neovim (in both normal and insert mode) and sending <BS>, despite the fact that it is mapped to :TmuxNavigateLeft.

:verbose nmap <C-h> produces the following:

n  <C-H>       * :TmuxNavigateLeft<CR>
        Last set from ~/.vim/bundle/vim-tmux-navigator/plugin/tmux_navigator.vim

<C-h> seems to work in Neovim, it's just sending <BS>, which I have mapped to gg, so it's putting my cursor at the top of the file I'm in. Which makes me suspect that something somewhere has mapped <C-h> to <BS> with nmap instead of nnoremap.

Using Vim instead of Neovim, there is no problem. Adding nnoremap <C-h> :TmuxNavigateLeft<CR> to my ~/.nvimrc doesn't help.

Dave Yarwood · Answer 11 · Sat Oct 10 2015 02:42:16 GMT+0800 (China Standard Time)

@megalithic Do you recall what exactly from that Neovim issue solved it for you?

Dave Yarwood · Answer 12 · Sat Oct 10 2015 03:01:45 GMT+0800 (China Standard Time)

Thanks!
infocmp $TERM | sed 's/kbs=^[hH]/kbs=\\177/' > $TERM.ti
tic $TERM.ti
That worked for me, thanks!!!

+1 on this -- it worked for me. It sounds like they are working on a fix for this in Neovim, something about upgrading the version of libtermkey that they use.

Seth Messer · Answer 13 · Sat Oct 10 2015 03:03:10 GMT+0800 (China Standard Time)

@daveyarwood SUPER late responding to you; sorry about that. yep, your tic block did the trick for me.

Henry Snopek · Answer 14 · Fri Oct 16 2015 08:03:48 GMT+0800 (China Standard Time)

be sure to run:

infocmp $TERM | sed 's/kbs=^[hH]/kbs=\\177/' > $TERM.ti
tic $TERM.ti

within your HOME directory

Chris Toomey · Answer 15 · Sun Oct 25 2015 07:40:58 GMT+0800 (China Standard Time)

@geoffharcourt I think I remember you sharing some comments around this recently. Can you shed any light on this for me (I'm not using neovim so not familiar with the issue).

Is there a clean solution we can recommend?

Geoff Harcourt · Answer 16 · Sun Oct 25 2015 21:11:28 GMT+0800 (China Standard Time)

I have <BS> in normal mode mapped to :TmuxNavigateLeft<cr> like this in my dotfiles. This solution fixes Vim/Tmux navigation, but should just be a bandaid until the Neovim team resolves their terminal keybinding issues. The issue has been open for months and doesn't seem to close to a consensus resolution yet.

There are some other solutions available, but they involve updating with tic, and I don't think we should be asking end-users to make those changes lightly.

Elliot Winkler · Answer 17 · Fri Nov 20 2015 06:25:28 GMT+0800 (China Standard Time)

I just had an issue with this too. Here's what solved it for me:

You have to fix Neovim somehow so that it doesn't override <C-h>. Updating tic as in this comment worked for me, but treating <C-h> as <BS> and mapping TmuxNavigateLeft to it would work too (hammer vs. scalpel).
Make sure you're using the tmux mappings described in the README. Originally I didn't do this because I was having some sort of issues with it, but everything seems to work great now.

Daniel Kesler · Answer 18 · Thu Jan 21 2016 02:24:07 GMT+0800 (China Standard Time)

If anyone has this problem with iTerm2 I found a solution here.
Specifically badeip says to go to
iTerm -> Preferences -> Keys
Add a new Global Shortcut Key. (Press +)
Press Ctrl+h as Keyboard Shortcut
Choose Send Escape Sequence as Action
Type [104;5u for Esc+

Nathaniel Watts · Answer 19 · Tue Feb 16 2016 04:24:54 GMT+0800 (China Standard Time)

~~@dckesler your solution worked for me 👍 !!~~

Actually - no dice when I don't have 2 vim splits open between Tmux panes.

If I have 2 split tmux panes, and vim is open on the left, and not open on the right - can't switch.

Nathaniel Watts · Answer 20 · Tue Feb 16 2016 04:52:55 GMT+0800 (China Standard Time)

I noticed that when trying control-h in prezto, it was enabling my vim bindings.

Removed that plugin and now 4;5u is output whenever using control-h in a tmux split.

Nathaniel Watts · Answer 21 · Tue Feb 16 2016 05:00:37 GMT+0800 (China Standard Time)

So, something in combination with removing this line in my .zshrc file, and this suggestion fixed things.

Hate that I don't know the exact ticket to get it working... will have to see if I can reproduce later.

Geoff Harcourt · Answer 22 · Tue Feb 16 2016 21:29:49 GMT+0800 (China Standard Time)

@thewatts it appears you have an involved enough setup with Prezto, etc. that you'd be best off bisecting your configuration to find the offending portions.

Start with the most vanilla configuration possible (comment out everything in your tmux.conf other than this plugin's required lines, disable any zsh tools like Prezto / oh-my-zsh / tmux plugin manager, etc.)
Demonstrate that the vim-tmux-navigator works in your terminal
Uncomment half of what's commented, test that it works
Roll back if the uncommenting breaks the plugin and then try uncommenting fewer lines.

One of the pitfalls of having a very involved setup (I say this as someone who runs a very large number of Vim plugins) is that debugging these problems takes a little time due to interaction across all the different things you've got in the mix.

Pablo Olmos de Aguilera Corradini · Answer 23 · Sun Mar 27 2016 05:01:18 GMT+0800 (China Standard Time)

The solution above about monkey-patching the terminfo, has to be run every time?

Geoff Harcourt · Answer 24 · Mon Mar 28 2016 22:47:24 GMT+0800 (China Standard Time)

@christoomey this is actually a Neovim issue with a long history and not anything specific to the plugin. I think we should close this issue out, folks can get involved in the discussion on the Neovim repo.

Chris Toomey · Answer 25 · Wed Mar 30 2016 00:05:58 GMT+0800 (China Standard Time)

@geoffharcourt I totally agree. Do you think you could write up a brief summary for the troubleshooting section of the README w/ link to this issue and or the neovim issue? Assuming it's not too much to ask, I've just added you as a collaborator so feel free to open as PR, or if you'd prefer, you can add the summary here and I'll add then we can close this issue.

Zack Hsi · Answer 26 · Thu Apr 07 2016 06:05:48 GMT+0800 (China Standard Time)

This fixes it perfectly for me:

if has('nvim')
    nmap <BS> :<C-u>TmuxNavigateLeft<CR>
else
    nmap <C-h> <C-w>h
endif

bernastoc · Answer 27 · Sat Apr 09 2016 01:24:24 GMT+0800 (China Standard Time)

(fixed, see below) Even without neovim/vim, I cannot jump to the left pane with ctrl-h with the provided modifications to .tmux.conf. This isn't solely a neovim issue and/or there are multiple issues. I'm using tmux 2.2.

Edit: I'm using mobaXterm to ssh to my workstation. In the terminal settings I unchecked "Backspace sends ^H" and this resolved my issue. I'm using neovim btw and no new settings required for this to work.

Geoff Harcourt · Answer 28 · Fri Apr 29 2016 22:08:43 GMT+0800 (China Standard Time)

@christoomey so sorry this took so long to get to, I haven't had much investment time lately. I've suggested #122 to update the documentation and link to solutions.

sinozhou · Answer 29 · Mon Jun 20 2016 11:26:43 GMT+0800 (China Standard Time)

I have the issue too when i switch termite to xterm.

so i adjust configure in .zshrc

in origin env

tmux
zsh
termite
vim

export TERM='screen' is fine!

my new env

tmux
zsh
xterm
vim

export TERM='screen-256color' is worked for me

Hadouken · Answer 30 · Sat Jul 22 2017 07:08:44 GMT+0800 (China Standard Time)

Has issue been fixed in 0.2.0?

kcajf · Answer 31 · Fri Dec 06 2019 04:38:49 GMT+0800 (China Standard Time)

@bernastoc did you ever get this working ? I'm in the same situtation - not a neovim issue, but just tmux - and also using MobaXTerm

bernastoc · Answer 32 · Fri Dec 06 2019 06:51:07 GMT+0800 (China Standard Time)

@bernastoc did you ever get this working ? I'm in the same situtation - not a neovim issue, but just tmux - and also using MobaXTerm

The second paragraph in my post describes what I did ;)

kcajf · Answer 33 · Fri Dec 06 2019 07:43:00 GMT+0800 (China Standard Time)

Ah, somehow missed that. Thanks!