vim-session VS distant.nvim

https://github.com/xolox/vim-session

I actually have in normal mode ,ss for save session and ,so for opening them. Central location of session dirs and that's it. Save session saves everything from files open, positions, tabs, you name it.

I'm looking to switch from vim-session to a Lua based session management plugin (i.e. :mksession wrapper). In awesome-neovim it looks like there are a couple of alternatives. I have relatively simple needs: I want a command for manually creating a new session, and automatic saving of an opened sesion when I quit Neovim. Bonus points for a built-in Telescope session picker, but I can always use (telescope_sessions_picker.nvim) otherwise. Do you guys have any advice?

You can use sessions to switch between different projects. They store your tabs, buffers, etc. Check out :help mksession. I personally use vim-session which is a wrapper around mksession which allows you to use it more lazily.

Check out :help :mksession. There's also a great plugin called vim-session that is a wrapper around :mksession making it easier to use, that adds commands like :SaveSession and :OpenSession that you can tab-complete to choose between all your saved sessions.

I started seriously using sessions a couple of months ago and it's awesome. Although the built in :mksession works I like to use vim-session which is a wrapper for :mksession that adds stuff like auto saving sessions on exit etc which I love.

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.