Sorry, you're right. The windows version I have is an old version that does not 
support netrw v153p. I will let you know if I get to test it on other 
platforms. Just to recap, this was the behavior I got on MacVim:

"It is now switching to the existing file as expected. One unexpected side 
effect is that after the switch the file is getting set as readonly. Also, the 
:E command (with or without a file open) when used with netrw is now displaying 
the output: "shell returned 1". I verified that with the old netrw the command 
doesn't display this output."

Btw, the "shell returned 1" warning is not failing the netrw command. It is 
just displaying this warning in the command line.

Thanks, 
Yavuz

On Thursday, July 31, 2014 3:24:51 PM UTC-4, Yavuz Yetim wrote:
> This was on latest Windows built. I just sourced the netrw.vba and that 
> created the vimfiles directory. I have some simple setup commands in the 
> .vimrc and I can check tomorrow if it works without this.
> 
> Yavuz
> 
> On Thursday, July 31, 2014 10:42:00 AM UTC-4, Charles Campbell wrote:
> > Yavuz Yetim wrote:
> > 
> > > v153p actually gives the following error on Windows:
> > 
> > > Error detected while processing BufReadCmd Auto commands for "scp://*":
> > 
> > > E117: Unknown function: netrw#Nread
> > 
> > >
> > 
> > That sounds like netrw was installed incorrectly.  Are you using some 
> > 
> > other tool which mangles the standard runtime setup?  Normally, 
> > 
> > netrwPlugin.vim ->.vim/plugin, netrw.vim -> .vim/autoload (and there's 
> > 
> > some syntax files, too) (on Windows, you may be using vimfiles instead 
> > 
> > of .vim).
> > 
> > 
> > 
> > Chip Campbell

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to