I find that "**" in &path causes my project (~6500 files in ~500
subdirs, in a local filesystem on a powerful machine with almost no
load) to take a LONG time when doing anything like :find - i can also
replicate this with :expand('**/*') or a similar :glob() call. :pwd
says I'm in project toplevel, :set path shows "path=.,,**".By contrast, find . -type f -print0 | grep -FZz Some/Path/File.pm returns almost instantly. As you'd expect. I'm using vim / gvim v7.2, built by Debian for 64 bit Linux. Is the "**" wildcard deprecated? Is the sort of slowness I see (just using :expand to list all files below . takes minutes) usual? I have been working on various projects using the same &path definition for years without issue. I'm unsure how to approach debugging this. A strace on the gvim process while it's hanging suggests it's poll()ing fd 5 (a socket..) like crazy. Any suggestions / tests / ways to rule out possibilities are gratefully accepted. If 6500ish files is too much for :find, is there a better option / workaround? Is this expected / usual behaviour? Is the ** wildcard performant? Thanks, /joel -- Joel Bernstein --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
