Thanks for pointing out those options. I now have password-less access.
However, I couldn't find an option that lets me set which terminal to use
when executing shell commands (is there a way to specify none?). It uses the
ugly cmd.exe, which has unreadable blue-on-black and makes me hit enter to
close the window. I'm use to rxvt, but the ideal solution would be having
vim not display any terminal.
Aside: how do I quote the vales I set options to? I tried single and double
quotes to no avail. Mainly I'm wondering because I currently need to set
bash to bash\ --login, so I have to quote the space.
I haven't had time to look into the NetOptionRestore issue yet. In the
meantime...has on one else encountered this problem before? I've barley
customized my vim installation, so I probably didn't introduce this problem.
As for the autocommand problem, I used an empty .vimrc and tried
buffer-switching from another buffer back to the scp file, but I get the
same issue. How would I disable this apparently default behavior? And why is
it there in the first place? I thought storage was what the buffer is for.
From: Charles E. Campbell, Jr. [mailto:drchip@...
Sent: Monday, May 03, 2004 1:39 PM
Subject: Re: Vim over SCP/SSH
>I'm using GVIM 6.2 on Win XP. When I try ":e scp://...", vim always scp
>directly via cmd (the exact command is: "C:\WINDOWS\system32\cmd.exe /c scp
>-q ... VIABD.tmp"), so I'm prompted to enter my key passphrase, when in
>I have cygwin's ssh-agent package (I have a bash script that automatically
>loads it for each new session, a la keychain). How can I make vim take
>advantage of this (or at least start bash instead of cmd)?
To use cygwin's bash, etc, I use (win2k):
in my <.vimrc>.
>Also, after hitting Enter to close the command window, I also get the
>Error detected while processing function <SNR>16_NetRead..<SNR>16
>E303: Unable to open swap file for "scp://y/blackboxloc", recovery
>Hit ENTER or type command to continue
Hmm, I don't see anything in NetOptionRestore() that uses a swap file.
I suggest activating the internal debugging statements. Get the latest
netrw.vim and also get Decho.vim from
as "Network Oriented Reading and Writing"
as "Decho, a vimL debugging aid"
to turn debugging on in <netrw.vim>. Then do a scp; a window should
show up with additional information as to what's going on.
>This shows up every time I save the file as well.
>Another annoyance is how vim always opens the file over scp again for some
>reason when I switch buffers. Why does it do this, when in fact the file
>should already be loaded?
That sounds like you have an autocmd (BufLeave, BufEnter, or something)
that is causing
the file to be re-loaded every time you switch buffers.