nvim-unception VS neovim-remote

You can also use the built-in terminal and use any terminal file manager you want. nvim-unception or flatten.nvim can be used to prevent nesting.

Flatten was inspired by nvim-unception, which accomplishes the same goal but can be difficult to configure in my opinion.

I’d look at how https://github.com/samjwill/nvim-unception does it.

This is my plugin. The relevant use case is demoed here from 30 seconds onwards. Basically, I block a terminal buffer forever until the git commit message buffer is BufUnloaded, which triggers an autocmd that unblocks the terminal buffer. However, it currently only works by opening the git commit message buffer in a new tab.

Try unception

I wrote nvim-unception and posted about it several months back; some people seemed to like it, even though it was still a bit rough around the edges.

I'm obviously incredibly biased, but since I prefer to use the built-in terminal emulator instead of Tmux for multiplexing and running quick bash commands, the biggest improvement for me personally was implementing a plugin that I wrote to quickly open files from inside the terminal buffer, and a keybind that I made to open a terminal window in the directory of the file that has focus.

U could use a plug plugin like nvim-unception to do what you are trying to do more efficiently.

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.