Note that there are some explanatory texts on larger screens.

plurals
  1. POTransparently edit remote files on Windows, with ssh/Putty and netrw
    text
    copied!<p>Ok guys, maybe this one has been asked before, but I searched and ran threw nothing, so i'm taking a chance here.</p> <p>I'm using the latest vim (gvim 7.3), on Windows 7 64bits.</p> <p>I've got some remote files that I want to edit directly with vim, using netrw.</p> <p>Right now, I've got a fully working transparent ssh connexion to my remote hosts, thanks to Putty, Pageant and public/private keys.</p> <p>I've successfully setup a read/write access to distant files with those fixes:</p> <pre><code>#### .vimrc #### let g:netrw_cygwin= 0 let g:netrw_scp_cmd = 'c:\"Program Files (x86)"\PuTTY\pscp.exe -q -batch' let g:netrw_sftp_cmd= '"c:\"Program Files (x86)"\PuTTY\psftp.exe' </code></pre> <p>Then I can access a file with :</p> <pre><code>:e scp:\\user@host:port\\home\me\some-file.txt </code></pre> <p>And, each time I access remote file, Vim run a windows prompt (cmd.exe) :</p> <pre><code>C:\Windows\system32\cmd.exe /c c:\"Program Files (x86)"\PuTTY\pscp.exe -q -batch -P 22 "C:\Users\me\AppData\Local\Temp\VIF215E.tmp" "user@host:/home/me/some-file.txt" Hit any key to close this window... </code></pre> <p>My problem is that hitting a key outside Vim each time I want to open/write a file isn't efficient at all.</p> <p>So my question(s) is(are) : </p> <ul> <li>Am I doing it the right way ? </li> <li>Is there another way of transparently accessing a remote file with ssh on Windows ? </li> <li>If no, is there a way to get rid of "Hit any key to close this window..." when Vim launches putty's pscp.exe ?</li> </ul> <p>Thanks a lot and happy vimming.</p> <p><strong>EDIT:</strong> Note to the <em>myself</em> in the past: <em>Dude, just go with linux and vanilla gvim/ssh. You'll thank me later (and take a look at spf13-vim)</em></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload