11–20 of 30 posts
Earlier quoted context omitted.
does sftp require configuration beyond what you've already got working if you're ssh'd in?
I mean you run that command locally. You aren’t ssh’d in, vim copies the file to a tmp location and you edit it, `:w` writes it back to the remote.
Earlier quoted context omitted.
I mean you run that command locally. You aren’t ssh’d in, vim copies the file to a tmp location and you edit it, `:w` writes it back to the remote.
Wow, I've been using Vim exclusively as my text editor now for 15 years and I did not know it could do this. Awesome!
If I’m reading this right, it’s “open a local vi(m) on a remote file”, by invoking a remote command. Is that right? I’m wondering how it’s different in effect to just using vim sftp://host/path/to/file
vi
Invokes gvim on your workstation,
passing it an scp://... URL of
the file(s) you wish to edit
suvi is neat, and bcp seems like something that I'd actually use.
If I’m reading this right, it’s “open a local vi(m) on a remote file”, by invoking a remote command. Is that right? I’m wondering how it’s different in effect to just using vim sftp://host/path/to/file
Discussion at the time https://news.ycombinator.com/item?id=1406145
It's quite fitting as a vim using HAM (with a callsign username), that the top comment on that thread is also a HAM saying how you can also do this in emacs. The world changes all around us, and yet it's always the same.
If I’m reading this right, it’s “open a local vi(m) on a remote file”, by invoking a remote command. Is that right? I’m wondering how it’s different in effect to just using vim sftp://host/path/to/file
Sure, but that makes all the difference. I often work on an embedded remote machine with quite restricted vim (can't use a custom config, particularly no language packages). When I am on the remote machine (typically I have to run local commands), I often discover I have to edit a python file (typically just minor edits). So to use vim sftp://host/path/to/file I have to open a new terminal copy the path and then open…
Earlier quoted context omitted.
Sure, but that makes all the difference. I often work on an embedded remote machine with quite restricted vim (can't use a custom config, particularly no language packages). When I am on the remote machine (typically I have to run local commands), I often discover I have to edit a python file (typically just minor edits). So to use vim sftp://host/path/to/file I have to open a new terminal copy the path and then open…
Can you install bcvi on that remote machine? (Genuine question - when I've been in similar situations, it also would have been a no-go to install a binary.