| Reading C:\Program Files\vim\vim72\vimrc_example.vim goes much faster | than reading ftp://ftp.vim.org/pub/vim/patches/7.2/README because the | former is on your computer and can be read extremely fast, the latter | must be transmitted over a network with limited speed and an | additional overhead to establish the connection. Even if the server is | on your own computer, getting a file via a server involves much more | overhead (before the first byte of the file can be read) than reading | a file directly in C:\path\to\filename.ext format your hard disk. | In addition, if Vim is set to put its swapfile in the same directory | as the editfile (which is the usual default when that directory is | writable), there is additional overhead if that file is at a remote | location. In that case, see the 'swapfile' and 'directory' options | about how to suppress using a swapfile for a given buffer, or placing | the swapfile at a different (faster-accessed) location.
Tony, I have eliminated other issues and isolated that it is in vim. I have tested without swapfile, and it gives the same pattern, and the same file is accessed fast in any method on e.g. notepad or using type.exe - and is loaded fast in vim if accessed with a drive letter rather than a UNC path... So it is very likely that it is something related to the leading double slashes. /H. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
