EDIT
Seems like there is a question as to why I have this setup. Per company policy I’m developing on a remote machine. The machine is Amazon Linux 2, which is not upgradable. We will not be switching to Amazon Linux 3, so I am stuck with it. Why to use neovim? It is my tool of choice and I have been using it for some time now. Why not use vim? I just prefer neovim. I’m following Linux philosophy, if you don’t like the way to the tool works, don’t adapt to the tool, use the one that works for you. And neovim just does it for me.
I tried compiling neovim natively on Amazon Linux 2, but there a ton of libraries that are missing there. And as I mentioned above, those I cannot upgrade. It is just how my company setup the image. Stupid? Maybe, but I can’t change it and unfortunately need to adapt. My solution, use docker. It seems to be working for my needs. I just have this pesky little problem that I would love to solve. So far, no luck. But I would appreciate any help with it.
ORIGINAL POST
I created a docker image based on fedora with neovim and tmux in it. The setup is identical to what I have on my local machine. Everything seems to be working except pane navigation. For that I’m using vim-tmux-navigator. I have it in my init.lua as well as in ~/.tmux/plugins/vim-tmux-navigator. In other words when I use mappings like , , , , I can’t navigate through nvim panes. The weird part is that I have no issues navigating through tmux panes. So it works in tmux but not in neovim. I can’t quite figure out what is the issue. The setup is identical to what I have on my mac. Can anyone advise on what problem could be and how I can fix it?
