neovim-remote VS tmux-resurrect

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.

I use https://github.com/tmux-plugins/tmux-continuum and https://github.com/tmux-plugins/tmux-resurrect to restore all my tmux sessions if I reboot my machine or kill tmux.

tmux-resurrect and tmux-continuum are the utils I use to persist sessions across reboots. They have keybinds and options to make it either automatic or manual, but they save EVERYTHING down to the Neovim session (if you use those) for the session's working directory

This would be my first go-to: https://github.com/tmux-plugins/tmux-resurrect

I hardly reboot a machine unless I am intending to, but there are plugins for tmux for this too.

https://github.com/tmux-plugins/tmux-resurrect

And to save and restore tmux sessions automatically, I use tmux-resurrect + tmux-continuum.

You must use all 3 of: tmux-continuum tmux-resurrect vim-obsession

Sure. Once you log in to the remote Linux machine, just run `tmux` and do your job. When you connect to the remote Linux machine next time, run `tmux attach`, and you will be right where you left off. The sessions will be persisted until you restart the Linux machine (well, or kill the tmux server). If you'd like even more persistence after machine restart, you can also try https://github.com/tmux-plugins/tmux-resurrect