Hugo Ahlenius wrote: > I have experienced an issue for quite some time, and now I > finally decided to deal with it - vim gets painfully slow > accessing files using UNC paths on Windows (paths that look > like \\server\share\folder \file). I have tested with Windows > XP and Vista on several machines.
I don't use Vim like that, so haven't encountered the issue. Some random thoughts follow. First, I have seen issues about slow access to UNC paths years ago (nothing to do with Vim). There was some well-known issue about network provider order which was particularly apparent when people had enabled the Microsoft software to allow access to NetWare servers. Also, the first access can be slow due to a need for network authentication after the server has timed-out the client. However, you are probably not seeing these. In Vim's source code, we find function fname_case() in file os_win32.c. I have noticed that function has an amazing trick. When you provide a file path name to Vim (on Windows), Vim wants to determine the correct case (the "true name") for each component of the path. Irritatingly, Windows provides no assistance, so Vim has to start from the root and search for the first directory in the root to determine its true name. That is repeated for each component of the path. I haven't looked to see what happens with a UNC path, but Vim might use FindFirstFile on the \\server and/or the \\server\share components (as well as on following directory components). That might cause various timeouts, or certainly a slowdown. I mention all this in the hope that someone is inspired to do a bit of testing. John --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
