-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
files
ignores input_delay
#145
Comments
Issue-Label Bot is automatically applying the label Links: app homepage, dashboard and code for this bot. |
See #140 . It's just slow, a performance issue of vim and vimscript. |
I know the search itself can be slow, but I want the search execution to be delayed until I have finished typing. That shouldn't be related to the above performance issue, is it? And it works fine for |
Since you have about 8000 files, vim-clap actually uses the built-in fzy python implementation, which runs synchronously, hence it could be slow. If you have more than 10,000 files, vim-clap will switch to the async way automatically. 200ms is not much sensible, try a higher value, you'll see that the execution has been delayed. |
I have tried |
Ok, I know the problem. vim-clap ignores the delay in this case. The original idea is to react fast if possible, for the providers like vim-clap/autoload/clap/popup.vim Lines 455 to 463 in 55b6df8
|
I did not find a better checker, now the delay always exists for vim. |
That's awesome and works perfect. Thank you very much for great maintenance of this gem 👍 |
Environment (please complete the following information):
Describe the bug
Although I have set the
g:clap_popup_input_delay
and it has 200ms default value, it doesn't seem to honor the value and does the search after each key press which makes it very slow on larger code bases.The grep command does
To Reproduce
see the screenshot part
Expected behavior
It should run the search after the given time value is passed
Screenshots
I'm not typing
test
one character at a time, it's Clap trying to do the search and since the code base contains too many files it takes some to do the search and return the result and does it again for the next characterThe text was updated successfully, but these errors were encountered: