vim-floaterm VS neovim-remote

Using https://github.com/voldikss/vim-floaterm and remap the same shortcuts to (un)toggle the terminal would be interesting for you, also about compatibility, because if tomorrow you use nvim in the terminal you have the same key maps.

vim-floaterm has wrappers around some terminal filemanagers.

If you don't like distro's and want to use something of your own, make sure that you have a few plugins like telescope.nvim, lazy.nvim, toggleterm.nvim Or vim-floaterm, gitsigns.nvim, which-key.nvim, which will make your neovim journey smooth. Again these are just few, but I highly recommend it.

My personal favorite is ranger, a multi-panel console file manager that works nicely in a Neovim terminal. I also use floaterm to get floating terminal windows for ranger and lazygit, but that's optional. A Neovim tab with a terminal would work equally well.

For simple tasks like opening a dirty file in nvim I prefer vim-floaterm. It has a really nice integration with a bunch of TUI tools.

The two obvious candidates are vim-floaterm and toggleterm.nvim.

I’d suggest taking a look at vim-floaterm. While I don’t use this feature, it should have the ability to do what you’ve described

vimwiki + floatterm + vimwiki-sync

Notice that this script depends on mhinz/neovim-remote: Support for --remote and friends. (github.com). (nvr as you have notice). The full-path is required to make it work.

I am currently using https://github.com/mhinz/neovim-remote with this bit in my zshrc:

Since they are on different screens I cannot use a single neovim instance (I tried playing around with neovim-remote but seems like that's for the usecase of opening files in one instance from different terminals -- doesn't help). Due to multiple LSP instances changes in one file are not reflected in the other, e.g., file B imports some types from file A; I create a new type in A but since B's neovim instance is not aware of any change to the A file corresponding the LSP fails to see the new type.

This version includes `nv` binary which is [neovim-remote](https://github.com/mhinz/neovim-remote) but rewritten in Rust (I've did it out of boredom) also with interface similar to `page`.

Practical use case: when navigating in ANY terminal (or tmux) write a function that sends opened files to a single running neovim instance instead of spreading opened vim instances all around like neovim remote does, but works for any terminal

I see the integration with neovim is done via a separate plugin, did you think about adding support for neovim-remote?

Another way of doing what u/TheLeoP23 suggested is by using https://github.com/mhinz/neovim-remote . This way you have a single neovim instance and you can open it on different terminals and mantain your current workflow.