WIP: Add persistent ssh connections #230
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With
:detachand:connect(currently in dev build of neovim) added it makes a lot of sense to have persistent remote connections, with remote-nvim acting as a dashboard for their management.This is a WIP with basic ssh connection spawning and UI.
Features:
Transfer of .config subdirectories is useful for external tools invoked form neovim e.g. yazi for file preview.
Global state is required for a dashboard, atm i've made rather minimal changes to ensure it's stable.
Currently spawning ssh sessions seems to work ok. I've used sockets for control over persistent ssh sessions and state
.jsonfile for additional connection info. Some additional system-wide sync should be added to ensure multiple instances of nvim don't mess with connection while it's being established.-ttflag is required to ensure the remote nvim is closed after the socket is closed.Any feedback would be appreciated.
I don't use docker or devpod so I cannot really assess if this workflow would work, but it seems possible, though I'm not interested in implementing it.
If you don't see this as a desirable direction for remote-nvim please let me know.