That is really incredible ideal plug-in. Actually I was plan to make that one. But I don’t know how to do this. Maybe I could have some reference on this plugin. 🥳🥳
quite similar to netrw and I'm sure faces the same challenges. neat project though. personally if I'm doing something advanced enough that working within ssh is not good enough, I will favour a deploy process over directly working on the machine. There are many companies that don't want you keeping any source code locally, so it has a place in solving a problem you wish you didn't have lol
I imagine the plugin wouldn't be for everyone :) At work, all of our code is on remote servers as it's too big to run and test on personal machines. Additionally, while this plugin does share similarities with netrw, there are a couple of distinctions. The first is that this plugin maintains a constant connection to a server (ssh or distant) through a shared library versus netrw's isolated calls to external programs like scp and sftp. The second distinction this video doesn't show - but the previous one did - is that this plugin supports remote process execution. This also supports using neovim's builtin LSP client with LSP servers located on a remote machine. I also use this plugin to isolate language servers and environments within docker containers so I don't need to install full dev environments on my laptop!
@@senkwich thanks for getting into details of pro and cons Vs netrw, I was wondering about this. Are you done with development of this now? I can see that the last meaningful commit is over a year ago and doesn't support current distant version..are you using something else?
@@CZiNTrPT ah, there's a v0.2 branch that is more up-to-date and works with the current release. There's just a little more that needs to be done with distant itself before the next release, then tweaking the branch. But features like remote shells and persistent connections do work!
Sorry, I'm not following your question. Ssh is used in one of two ways: executing `distant listen` on the remote server so you can connect to a distant server or providing a client experience where you can read/write files and run programs on the remote machine without needing the distant server. The distant server binary isn't copied over to the remote machine for you. Are you asking if a feature could be added to have the plugin automatically install the distant server binary on the remote machine while you are ssh'd into it? If so, I had an issue open for it: github.com/chipsenkbeil/distant.nvim/issues/1 I closed that issue as out of scope for the plugin.
Hey there! You'll find that there are different reasons to use sshfs versus this approach. For my own work, sshfs isn't an option. Check out github.com/chipsenkbeil/distant.nvim/issues/33 for a comparison!
There are reasons to use sshfs and there are alternative reasons to use something like this! For your use case, sshfs may be perfect. Check out github.com/chipsenkbeil/distant.nvim/issues/33 for a comparison.
There are actually advantages and disadvantages to sshfs vs this approach, if you can believe it! :D Where your remote processes run, stability and automatic reconnections, etc. I've captured that exact comparison here if you want to read more: distant.dev/editors/neovim/faq/#how-does-this-plugin-differ-from-using-neovim-with-sshfs
This is marvelous. I didn’t know I needed this until now
really liked your explanation and setup instructions. TJ sent me here :)
I'm so happy to see this! Thank you!
This is amazing, wow. So much progress has been made, good job
That is really incredible ideal plug-in.
Actually I was plan to make that one. But I don’t know how to do this. Maybe I could have some reference on this plugin. 🥳🥳
This is absolutely fucking amazing.
Hey... silly question - what's that font you're using? I like the curviness soo much 😊
Replying to an old comment here, but I think it was github.com/belluzj/fantasque-sans !
nice work 👍👍
nice tool, thanks
quite similar to netrw and I'm sure faces the same challenges. neat project though.
personally if I'm doing something advanced enough that working within ssh is not good enough, I will favour a deploy process over directly working on the machine. There are many companies that don't want you keeping any source code locally, so it has a place in solving a problem you wish you didn't have lol
I imagine the plugin wouldn't be for everyone :) At work, all of our code is on remote servers as it's too big to run and test on personal machines.
Additionally, while this plugin does share similarities with netrw, there are a couple of distinctions.
The first is that this plugin maintains a constant connection to a server (ssh or distant) through a shared library versus netrw's isolated calls to external programs like scp and sftp.
The second distinction this video doesn't show - but the previous one did - is that this plugin supports remote process execution. This also supports using neovim's builtin LSP client with LSP servers located on a remote machine.
I also use this plugin to isolate language servers and environments within docker containers so I don't need to install full dev environments on my laptop!
@@senkwich thanks for getting into details of pro and cons Vs netrw, I was wondering about this. Are you done with development of this now? I can see that the last meaningful commit is over a year ago and doesn't support current distant version..are you using something else?
@@CZiNTrPT ah, there's a v0.2 branch that is more up-to-date and works with the current release. There's just a little more that needs to be done with distant itself before the next release, then tweaking the branch. But features like remote shells and persistent connections do work!
Very cool. One suggestion - can't you make it optional to use the ssh session as scp and copy the distant binary to the remote?
Sorry, I'm not following your question. Ssh is used in one of two ways: executing `distant listen` on the remote server so you can connect to a distant server or providing a client experience where you can read/write files and run programs on the remote machine without needing the distant server.
The distant server binary isn't copied over to the remote machine for you. Are you asking if a feature could be added to have the plugin automatically install the distant server binary on the remote machine while you are ssh'd into it? If so, I had an issue open for it: github.com/chipsenkbeil/distant.nvim/issues/1
I closed that issue as out of scope for the plugin.
@@senkwich That's exactly what I meant. Thanks anyway.
May I ask if that upper status bar is tmux or something like zsh?
It's from tmux.
How is this any different than using sshfs to mount a directory on a remote server?
Hey there! You'll find that there are different reasons to use sshfs versus this approach. For my own work, sshfs isn't an option.
Check out github.com/chipsenkbeil/distant.nvim/issues/33 for a comparison!
I miss DistantSuns.
.
Why not support username as part of the URI? Eg root@IP
Easier to work with programmatically. Could be added to the parser for vim commands, but it isn't a priority for me at the moment. :)
just sshfs?
There are reasons to use sshfs and there are alternative reasons to use something like this! For your use case, sshfs may be perfect.
Check out github.com/chipsenkbeil/distant.nvim/issues/33 for a comparison.
font?
For my terminal? I typically use Fantasque Sans Mono, although I can't remember if this terminal was using it.
Or you could just use sshfs :)
There are actually advantages and disadvantages to sshfs vs this approach, if you can believe it! :D Where your remote processes run, stability and automatic reconnections, etc.
I've captured that exact comparison here if you want to read more: distant.dev/editors/neovim/faq/#how-does-this-plugin-differ-from-using-neovim-with-sshfs
@@senkwich Thanks, I'll check it out.
tcp
yep