Navigator.nvim VS move.nvim

If screen real estate is not an issue I prefer multiple panes and having neovim zoomed in when Im mostly coding. I also recommend setting up neovim and tmux so that moving between tmux panes and nvim windows is done transparently with the same key combinations. See this snippet in my tmux config that enables that on the tmux side: https://github.com/eclbg/dotfiles/blob/main/tmux/tmux.conf#L31 And you'll need Navigator.nvim so you can move out of nvim and into tmux

Moving left and right between Neovim and Wezterm panes was a pain (no pun intended), and especially so since the existing navigator.nvim integration wasn't able to detect that nvim was the foreground process in some scenaros.

if I'm not mistaken navigator does help with switching between nvim/wezterm panes

Do you by chance use this plugin: https://github.com/numToStr/Navigator.nvim/wiki/WezTerm-Integration

Thanks for doing this. I dropped Tmux for Wezterm's native panes earlier this year. Glad WezTerm finally added the support for this. However, I think there may be a mistake in the Wezterm config in your wiki.

especially Navigator.nvim?

I open a tmux split pane, or a floating terminal window in Neovim for one-off commands. I also use Navigator.nvim for seamless navigation between Neovim splits and tmux panes.

Source: https://github.com/numToStr/Navigator.nvim

there is also move.nvim which also allows you to move a visual block like that: https://github.com/fedepujol/move.nvim

The author of move.nvim has inactive his repo (https://github.com/fedepujol/move.nvim) and now this plugin comes, thanks so much <3

I've just updated my plugins and noticed that fedepujol/move.nvim was giving me an error.

I was trying to find a clean, concise way to set up my mappings through legendary.nvim for move.nvim which has separate commands for normal vs. visual mode. I didn't want a separate line for each mode (which before would be needed because different commands would be run based on the mode).