netman.nvim VS distant.nvim

Hello Neovimers :) I posted this on the netman repo as well but I just wanted some opinions from users who use netman.

Lazy self promotion of netman.nvim which is designed to give you browse (and edit/read access) of remote systems without actually needing any configurations on said remote systems :)

I haven't been super active lately but Netman.nvim is my attempt to give neovim a solid remote editing experience. I've been taking a bit of time to myself though but it's still relatively stable for ssh and docker.

If you are really interested in doing this yourself with loop, you should take a look at either plenary.job or netman.shell (I made the latter) as both are very well documented.

If there are any users of Netman already that also use windows (or users of Neovim that want to use Netman but can't because they are on a windows machine), please checkout the windows-compat branch!

Does that not write out to the current pty? That is an issue I have been facing with generic ssh support in netman. I have yet to come up with a decent solution to it :(

A quick bullet point list of features that are included in this point update - Mostly complete Neo-tree integration - Moving files and directories between hosts (including between docker containers and ssh servers) - Auto opening your remote "home" directory in ssh - A complete rewrite of how our "integration" with neovim works - A completely new logging system - A new event system

The password issue is currently something I am looking to address in netman though exploration into the area has proven unfruitful so far :/

Netman supports remote editing of files over ssh.

Oops, meant distant, https://distant.dev/.

2) There is a remote working plugin to not have the overhead of sshfs copying around files https://github.com/chipsenkbeil/distant.nvim, but you could also role your own with neovim now having remote mode and lua runner. Main caveat is how to get consistent file system view.

- What do you think of other plugins e.g.: https://github.com/chipsenkbeil/distant.nvim?

This is something I've been tracking pretty closely. My understanding of the current options: 1. Use sshfs. Pros: nothing to install on the remote server. Cons: will choke on huge filesystems when doing some operations (e.g. fuzzy finding). Also requires all your LSP/linting/analysis tools to be installed locally, which may not be the case if your company is transitioning to remote developer environments. 2. Use netrw or similar. Pros: nothing to install. Cons: will not play nice with LSP, fuzzy finding, or anything else. 3. Use distant.nvim. At this point, basically the same as netrw except that maybe remote LSP will work. 4. SSH to the server and use nvim there. Pros: simple and everything works. Cons: Have to install nvim on the server. SSH connection may cause typing lag if the RTT is high (some people report that Mosh can help the lag issue)

The reason being is that I've written a service called distant with a companion neovim plugin, distant.nvim, and want to provide forms of authentication in the same vein as ssh.

Did a lot if research. there is distant.nvim that tries to solve it maybe it will work for you.

I either use the vi / vim that's on the server or connect remotely using https://github.com/chipsenkbeil/distant.nvim

Regarding the last part of your comment: you may get some value out of this plugin, https://github.com/chipsenkbeil/distant.nvim, https://www.youtube.com/watch?v=wVAsbpByQ3o.

I've not used it but your use case made me wonder if there's a nice way to do it, as I regularly SSH into my NAS and RPi's, so I had a quick search.