Tune performance of palette file searches

With these changes I can use the palette file search on the chromium source code. I also fixed what I think is a bug in the debouncing.
No worries, I'm in Seattle so we're pretty laid back about "today" 
anyway. Let me know if it works okay, and if it becomes a problem it's 
not a huge change. We can also probably make the result limit 
configurable--I've thought it might be nice to let people ask for more 
if they're not working on very large lists, I just never got around to 
setting up the styles for it.

On 2014-06-12 15:51, Ben wrote:
>> 
>> +        //now find fuzzy matches
>> +        if (results.length < findResultsLimit) {
>> +          var fuzzyMatches = this.files.filter(function(path) {
>> +            var baseName = path.split(/[\/\\]/).pop();
>> +            return !exactBeginsBase.test(baseName) && 
>> !exactInBase.test(baseName)
> 
> I had it like that originally but changed it as I wasn't limiting the
> results then and it was unusable. With the results limit it should be
> fine, but I'll test it today to make sure. I can put up another pull
> request once tested.
> 
> BTW I'm in Sydney so my 'today' is probably not your today :)
> 
> 
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/thomaswilburn/Caret/pull/238/files#r13731455