-
-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot disable fuzzy matching #169
Comments
I did this by using the :custom keyword in use-package, like this; |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behavior
I'm trying to disable fuzzy matching, since it results in far too many candidates in medium to large projects. I've attempted to do so by both customizing
helm-projectile-fuzzy-match
, and also trying tosetq
it, but neither seems to have an affect.Actual behavior
I'm not actually sure if this is even fuzzy matching, or maybe just a bug or misconfiguration: it appears to just be matching an arbitrary number of characters between the characters of the query. So if my query is
term
, it is seems to be matching.*t.*e.*r.*m.*
, which is not a kind of fuzzy matching I'm familiar with. In any cases, it produces too many results which are not useful. Here ishelm-projectile-find-file
:Steps to reproduce the problem
Search for something with
helm-projectile-find-file
.Environment & version information
helm-projectile
version:20220820.826
helm
version (inhelm-pkg.el
):3.8.7
projectile
version (M-x projectile-version
):20220828.1421
M-x emacs-version
):GNU Emacs 28.2 (build 1, aarch64-apple-darwin21.1.0, NS appkit-2113.00 Version 12.0.1 (Build 21A559))
Mac OS X 12.6
The text was updated successfully, but these errors were encountered: