Skip to content
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

query input searches inmediately after each keypress #555

Closed
diddierh opened this issue Jul 6, 2016 · 4 comments
Closed

query input searches inmediately after each keypress #555

diddierh opened this issue Jul 6, 2016 · 4 comments

Comments

@diddierh
Copy link

diddierh commented Jul 6, 2016

When the query input is used this searches in the entire docsets for each partial phrase that is formed while the final phrase is typed, this makes the searches tedious because each search is slow and the intended search is the most of times for the final full phrase.

I suggest that after a keypress and before doing a search a period of time must pass (usually one second), this for waiting a new keypress.

@mrhota
Copy link

mrhota commented Jul 17, 2016

related to #559 (which rebases #460). Searches are so fast with that code that this may not be an issue once that gets merged.

@trollixx
Copy link
Member

Fixed in fd11923.

@trollixx trollixx added this to the 0.3.0 milestone Jul 20, 2016
@diddierh
Copy link
Author

tested work as intended, thanks

@lock
Copy link

lock bot commented Sep 16, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for a related request.

@lock lock bot locked and limited conversation to collaborators Sep 16, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

3 participants