Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

Exact starts-with should take precidence #41

Open
timscott opened this issue Jun 3, 2014 · 12 comments
Open

Exact starts-with should take precidence #41

timscott opened this issue Jun 3, 2014 · 12 comments

Comments

@timscott
Copy link

timscott commented Jun 3, 2014

To replicate:

  1. Open a tree containing files cox.rb and context.rb
  2. cmd-p and type "cox".
  3. Fuzzy finder lists context.rb above cox.rb

Perhaps not wrong but certainly surprising.

@alexrussell
Copy link

👍

@benzen
Copy link

benzen commented Jun 26, 2014

👍

@collinbrewer
Copy link

👍 This is a must!

@albertorestifo
Copy link

This feature is overdue in my opinion

@bprosnitz
Copy link

+1 Exact searches sometimes don't match

@paulcsmith
Copy link

👍

@gdaolewe
Copy link

gdaolewe commented Oct 5, 2015

👍 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.

@benzen
Copy link

benzen commented Oct 6, 2015

I would argue that it's quite frequent to prefer matching at the end of the
file path than anywhere at the begining.
I mean the file name it almost always the only part of the path that i can
recall

2015-10-05 17:11 GMT-04:00 gdaolewe [email protected]:

[image: 👍] 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.


Reply to this email directly or view it on GitHub
#41 (comment).

Benjamin DREUX

@bronson
Copy link
Contributor

bronson commented Oct 10, 2015

Related to #98 no doubt.

@izuzak this feels buggy to me. Not sure I agree with the enhancement label.

screen shot 2015-10-10 at 4 12 29 pm

Yes I want job_spec.rb... that's what I'm typing ain't it? :)

@timscott
Copy link
Author

@broson Yes, this is the exact case. Because of this, a simple starts-with search would be better like 80% of the time.

@gdaolewe
Copy link

@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.

@benzen
Copy link

benzen commented Oct 27, 2015

Maybe I badly explained myself, but I totally agree with @gdaolewe

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

10 participants