-
Notifications
You must be signed in to change notification settings - Fork 201
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
Sorting is too aggressive instead of favoring "closest" match #365
Comments
There was a bug causing us to always fuzzy match on the label, which broke the prefix bonus for this LSP since it includes a space/dot icon. We're also now using the hints that LSPs provide for sorting. Hopefully the sorting looks a bit better on |
So main has better sorting and all the matches with _ or __ first will not appear first compared to what should show up? Should I just wait for a stable release on this for the sorting to be fixed? Thanks. |
Make sure you have done the following
blink.cmp
Bug Description
I recently switched to blink.cmp as nvim-cmp feels too slow.
One thing i miss from nvim-cmp is how good the completions were as they favored the "closest" item.
Here is an example from nvim-cmp using clangd:

the results are almost perfect as you can see.
Here is the same example but in blink:

it picks out some functions, but then the types are in alphabetical order which doesn't really make much sense.
I also recreated a similar scenario in fzf and as you can see it picks out int correctly.

(i will add more examples when i have time)
Relevant configuration
neovim version
v0.10.2
blink.cmp
version: branch, tag, or commitv0.5.1e
The text was updated successfully, but these errors were encountered: