Monday, December 30, 2013

Re: Netrw issues with tempfiles under gVim + Cygwin

Charles E Campbell wrote:
> esquifit wrote:
>> On Sunday, December 22, 2013 10:45:01 AM UTC+1, esquifit wrote:
>>> One of the issues is
>>> that Netrw isn't able to download files through http.
>> To be more precise:
>>
>> :e http://host.com/foo
>>
>> is working fine, while
>>
>> :Nread http://host.com/foo
>>
>> gives an error:
>>
>> **warning** (netrw)
>> delete(/cygdrive/C/Users/esquifit/AppData/Local/Temp/VIBEFC.tmp) failed!
>>
>> The current buffer is set to read-only and no content is loaded into
>> it, even if the content has actually been downloaded and available in
>> the above file.
>>
> Please try v150m - there's a new setting-variable, g:netrw_cygdrive
> (default value: "/cygdrive").
>
> g:netrw_http_cmd is set by default to one of the following:
>
> elinks
> links
> curl
> wget
> fetch
>
> Each is tested in the order given, and the first one that
> executable("...") returns a 1 on is used. Your problem with
> g:netrw_http_cmd is, in fact, because executable() is not returning a
> 1. Look into paths, or manually set the variable.
>
> The Nread http://host.com/foo issue --- well, I'm getting a different
> problem, so I'll look into it.
>
I've figured out what my "different problem" was caused by, and am now
issuing a new warning. I'd opened the a directory using netrw, then
tried using :Nread ... and that was, of course, attempting to read the
file into the netrw buffer (which is not modifiable). I don't believe
that the problem I just fixed is pertinent to the problem you're having.

Regards,
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 vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

No comments: