bob VS distant.nvim

That depends on the debian stable repo what version of Neovim they provide. My suggestion would be to check out bob, which as far as I'm concerned it's the easiest way of installing Neovim and gives you the ability to switch between stable and nightly.

Config details: 0. Distribution: AlmaLinux 9 (what I'm forced to use at work) 1. Also requires: git, curl, clang, rustup, fzf 2. neovim version manager: https://github.com/MordechaiHadad/bob 3. I'd like to use the LazyVim setup 4. using an nvims() shell function to switch between setups (default & LazyVim, for now) (see https://gist.github.com/elijahmanor/b279553c0132bfad7eae23e34ceb593b)

Auto-install of Bob Neovim version manager (optional)

I personally use bob, ($ cargo install bob-nvim), and it's been great for ease of version management, including nightly

Honest just use bob on non-bleeding edge distro

There's already bob (Version manager for Neovim)

I use on all platforms: https://github.com/MordechaiHadad/bob

current stable is 0.8.3 maybe try the unstable ppa or appimage or bob.nvim

If you want to peek at it now, you could try a neovim version manager like bob... https://github.com/MordechaiHadad/bob I've been using it recently and it makes experimenting with new stuff a bit easier. Then if you run into issues you can switch back to a stable release. I'm considering doing a video on this too since I think it would be helpful to some... and I don't think it's very well known

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.