FTerm.nvim VS neovim-remote

To achieve our goals of fingertip access nirvana, we are going to be using a plugin called FTerm.nvim.

i use F2 to toggle Fterm

IIUC this request https://github.com/numToStr/FTerm.nvim/issues/67 is also similar to your use case. I might implement this in FTerm.nvim but I have to study the client-remote thingy.

Have you checked out https://github.com/numToStr/FTerm.nvim?

gitui inside FTerm.nvim has been my preferred method to interact with git from within nvim. gitui has indeed proven to be a great frontend to git.

I did a bit of hunting and came across FTerm.nvim and I immediately notice that it is created and maintained by numToStr who also maintains Comment.nvim which is my preferred Neovim commenting plugin, which has always always worked great.

If you’re talking about the terminal inside a floating window, I think fterm.nvim is one which people commonly use.

I use https://github.com/numToStr/FTerm.nvim since you can specify in the setup which shell to use

It only work for very simple situation (project with only one build target), but it quite save a lot of time for me. For much complex situation, I prefer to write a singe bash script for specific project, and run them in FTerm

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.