Case sensitivity bugs

[alvinchow86]

It seems that once you've finished a "word", it gets removed from the list of candidates. But then what happens is if you hit "tab", what you've typed will get completely replaced with a very different word.

Here's an example in Java, with the words thread and Thread. When you start typing say the first few characters of thread, the primary suggested match is thread as expected, but when I type the last letter (d), it suddenly changes to Thread. Exact opposite thing happens when typing Thread.

Also in general, I think matching case should take higher priority for selecting the first match, or at least there should be an option. In this example, I think downloadThread should be the main suggestion instead of DownloadTask.

[peterbe]

I think downloadThread != DownloadTask and when you type dow it should NOT recommend DownloadAnything.

[saschagehlich]

Sorry, but I disagree. It's not a bug, it's a feature and I'm using it a lot.

I'll add a case sensitivity option, though.

[bblack]

👍 Case-sensitivity option is nice, but regardless, I think case-sensitive matches should appear higher in the list.

[janmarek]

Case sensitive matches should definitely have higher priority.

[jeancroy]

There are two issue in alvinchow86 post.

First two screenshot:
Both thread and Thread exist in the suggestion list but auto-complete remove suggestion that is exactly the same as typed. That mean you cannot accept a result from suggestion list and not change something. Pressing tab accept the first result.

Last screenshot:

Order of the results is handled by fuzzaldrin.

• Now fuzzaldrin do have a preference for proper case !
• However it also have a preference for shorter string.

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.

PR atom/fuzzaldrin#22 would make fuzzaldrin (and thus autocomplete) more like you expect regarding case sensitive results. For example see this test

[glen-84]

+1

At a minimum, it should show matching case results first.