One problem that puzzles me is that netrw is slow even accessing folders in my HD. Is the cause well known, and is there any low-effort way to prevent this? I am in a locked down environment, so I'm limited to older versions of vim and netrw:
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Oct 27 2010 17:59:02)
MS-Windows 32-bit GUI version with OLE support
Included patches: 1-46
netrw v140
Thanks.
I know the listing style (:help g:netrw_liststyle) can affect browsing speed.
Besides that, unless you are unable to write changes to your user HOME directory, you are certainly NOT limited to upgrading netrw. Are you able to write your own Vim config files? If so, you can install Vim plugins, meaning you are perfectly able to upgrade netrw.
Thanks, I just looked it up. netrw_liststyle corresponds to pressing "i" to change the listing style. It's still odd that this should matter when looking at the local HD. So I'm wondering if netrw queries all letter drives at a top level, or causes Windows 7 to do this. Using "i" to change the liststyle seems to be quick on some styles, but this isn't all that repeatable i.e., a style that is fast one time isn't always fast.
It's strange but I found that neither netrw_liststyle nor g:netrw_liststyle changes when I press "i". Letting netrw_liststyle or g:netrw_liststyle doesn't affect the listing style either, even if I update the list withe ":e".
With regards to upgrading plugins, I've been down this path a number of times in the past, and invariably, the new netrw requires a more recent version of vim.
In case this sheds any light on the problem, "q:" to bring up the command history also incurs a multi-second delay.
Oops. Found the problem. Needed to remove a network letter drive from my rtp. Hope this helps someone...
OK, thanks for that. I don't think I'd want to re-use directory
listings, since I'm usually changing stuff in it. Also, these network
drives are mapped to letter-drives -- I'm not sure if such directories
under those letter drives are considered "remote". Besides, clearing
out network drives from the rtp seems to have solved the problem.
>> With regards to upgrading plugins, I've been down this path a
>> number of times in the past, and invariably, the new netrw requires
>> a more recent version of vim.
>
> The latest netrw needs vim 7.3.465 (ie. 7.4 is fine).
Yes...sigh...I can do it at home, but not elsewhere.