-
Notifications
You must be signed in to change notification settings - Fork 128
Exact starts-with should take precidence #41
Comments
👍 |
👍 |
👍 This is a must! |
This feature is overdue in my opinion |
+1 Exact searches sometimes don't match |
👍 |
👍 Large project with a lot of files, exact matches are often buried by results that have several of the search characters but spread far apart. This makes fuzzy finder almost less useful than if it weren't fuzzy at all. |
I would argue that it's quite frequent to prefer matching at the end of the 2015-10-05 17:11 GMT-04:00 gdaolewe [email protected]:
Benjamin DREUX |
@broson Yes, this is the exact case. Because of this, a simple starts-with search would be better like 80% of the time. |
@benzen I agree that it should prefer matching the filename rather than the path, but it should prefer matching towards the beginning of the filename itself. If the matching is done on the full path + filename as one string, I think that's quite wrong. I don't know how many I speak for, but I almost never type part of the path to find a file; the only reason I would is this exact scenario, where typing the filename exactly puts the desired file way down in the suggestions and I have to start typing the path to disambiguate. |
Maybe I badly explained myself, but I totally agree with @gdaolewe |
To replicate:
cox.rb
andcontext.rb
cmd-p
and type "cox".context.rb
abovecox.rb
Perhaps not wrong but certainly surprising.
The text was updated successfully, but these errors were encountered: