> FWIW, I find the whitelisting approach detailed in the linked gist
> both elegant (this is rare in Vimland) and effective, so I don't think
> this would be needed.
Right, using 'wildignore' for this should just work.
It appears the remaining issue is performance. Currently when
'wildignore' contains something like "*/.git/*" then all files in and
below a ".git" directory will be discarded. But the search in this
directory still happens, and can take quite a bit of time.
Without changing the options, the implementation could check for
encountering a directory which will have all matches discarded by
'wildignore' and do not scan that directory. This needs to be done
carefully. And avoiding expanding matches into a full path and
compiling the patterns in 'wildignore' when no match is possible,
otherwise we make other cases slower.
--
Contrary to popular belief, Unix is user friendly.
It just happens to be selective about who it makes friends with.
-- Dave Parnas
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
/// \\\
\\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_dev" 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_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/20230603115419.196AF1C0595%40moolenaar.net.
