Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Case sensitivity bugs #42
There are two issue in alvinchow86 post.
First two screenshot:
Order of the results is handled by fuzzaldrin.
And that is what explain current order.
The thing is, fuzzaldrin, while considering both factor, is HEAVILY biased toward shorter string. For example a single extra character is enough to prefer wrong case. See atom/fuzzaldrin#17.
Only sometimes true.
For example typing
Both matching case result are slightly worse than case-insensitive one.
However because both
I believe that's the convention vim YouCompleteMe use. (Actually only uppercase are forced case sensitive for YCM). I cannot immediately think of a counter example, nor a case where it would be needed on top of atom/fuzzaldrin#22 strategy.
For that PR, I went over like 50 real life issue of wrong ordering and added soft rules to fuzzaldrin. By soft rule I mean detect signal of match quality, and add bonus accordingly. Proper case are involved in many bonus, for exact case, acronym, exact substring etc. If you find a use case that is not covered by that PR, i'll be happy to either tweak bonus weight or add a new soft rule.
As for the proposed rule, it cannot be used to enforce all lowercase match like asked here: atom/fuzzaldrin#17. And also it might be confusing because typing a single uppercase letter can change the meaning of every other typed letter so far.
How is this not a bug? :D
Reminds me of having autocorrect on in Skype as in it makes more incorrect corrections than the people using it make typos. I'm not saying fuzzy matching is a bad thing, and I don't want to disable it, but this can't be right, I get bitten by this several times per hour.