neovim-remote VS vim-dispatch

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.

Tis is good for the compilation to make it async( otherwise it blocks) https://github.com/tpope/vim-dispatch it wraps around the built in make/makeprg feature. Would recommend that you dont do it with large builds/outputs.

vim-dispatch by the legend Tim Pope. send the task to the background, keep using editor. once the task is finished, it output to qflist buffer

The other answer here covers everything you need, but if you want a plugin-based solution you might be interested in vim-dispatch which runs command line tools asynchronously, and offers the option to run the command in the background instead with :Dispatch!.

You should check :h compiler :h make and :h 'errorformat'. You could also check vim dispatch, a plugin that enhances this features

Also plugin supports asynchronous execution (using terminal, jobs or vim-dispatch).

Do note that :make is blocking, and you need to wait until it finishes before it sends you back to the editor. If you want it to be asynchronouns, you can install vim-dispatch + vim-dispatch-neovim for Neovim support in vim-dispatch.

if you want something to work out of the box, is async and is already configured per language, check out TPope's dispatch

For long-running programs, like compiling, or running full test suites, or running terraform on a decently sized infrastructure project, I may run them with :Make (courtesy of tpope/vim-dispatch) so I can keep working on the project while the external program is running. If I'm in an environment without vim plugins, I may spawn a new tmux pane/window. As a last resort, I will ctrl-z/fg if I don't have tmux on the remote system (e.g. dev containers).