-
Notifications
You must be signed in to change notification settings - Fork 285
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
Set the default 'Wait before searching' time to 0.00s #340
Comments
I only came across this when dealing with the bug I tried to fix in this Does anyone know why you would have this set to anything other than As per Phil's suggestion, we could remove this option all together, and then It definitely made QS feel a lot 'snappier' for me. On 30 May 2011 01:04, philostein <
|
I’ve always assumed it was there for slower machines. That is, if it takes a while for results to come back, you might want it to wait until you’re done typing to start the search instead of cranking away on stuff you don’t want. Maybe this isn’t as much of an issue as it was in 2003. :) |
With my machine being significantly slower (Since upgrading to Lion) I am actually seeing a requirement for this setting now. I use a value of about 0.05s, which seems to help significantly with loading objects, so I suggest we change the QSDefaults value from 0.1s to 0.05s. I will issue a pull request soon if I hear no objections. |
Sounds fine. |
Time has been halved to 0.05s, this will be present for new users only. |
Preferences>Preferences>Command>Wait before searching>0.00s
After trying Patrick's hint on twitter, QS got significantly faster for me. The default is 0.1s (according to Patrick).
I thought the time delay concerned searches appearing in the results list, not the actual search time.
I reckon this would benefit a lot of users if it's a viable change. (My Intel MacBook is 5 years old.)
The text was updated successfully, but these errors were encountered: