Auto-complete sort does not prefer exactly matching prefix

[dnrce]

Migrated from the original issue at https://www.assembla.com/spaces/tracks-tickets/tickets/1161

The results from auto-complete do not put the match that has the exact prefix on top.

This bothers me, because my system has an unique two-letter code for each context to quickly enter actions. For example, I have the following contexts:
sc Steven - Computer
mc Meike - Computer
ac Allebei - Computer
Ongesorteerde acties

The last context is used to dump actions in for later processing. Now, suppose I enter a new action that I want to put in "Allebei - Computer". I'm used to typing "ac" in the context field, waiting for auto-complete to offer suggestions and then hit return to accept the first match. However, the first match will not be "ac Allebei - Computer" (the expected result) but "Ongesorteerde acties" (which also contains 'ac').

What should the sort order be? Am I right that exact prefixes should be preferred? Where in the code is this dealt with?

Originally reported by zteven on May 5, 2011 at 08:07:29 (-0700)

[dnrce]

On May 5, 2011 at 10:14:25 (-0700), lrbalt commented:

I'd rather not change this right before the release. The code is generic and uses include? construct for ruby strings, see app/controllers/application_controller.rb on line 110, which is called from the context_controller and project_controller in the index methods

[dnrce]

On May 5, 2011 at 10:16:02 (-0700), lrbalt commented:

try putting a @ sign before the ac, so you can type @ac