-
Notifications
You must be signed in to change notification settings - Fork 174
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
LSP autocomplete should support fuzzy search #5511
Comments
Hello @veksha , can you see it please? |
Moved to #5513 by Alexey |
1 similar comment
Moved to #5513 by Alexey |
My function I tried to reuse it for LSP. here: def filter(self, item, word):
s1 = item['label'] if item.get('filterText') is None else item.get('filterText')
s2 = word
pos_bracket = s1.find('(')
s1 = s1 if pos_bracket == -1 else s1[:pos_bracket]
print('filter for:', s1, s2)
return is_fuzzy_match(s1, s2) don't work! |
So the fuzzy is requiring the server support and/or some LSP client option must be changed. this is for @veksha , please. |
I dont see in web-search how to allow fuzzy in LSP servers settings for other editors. maybe only few servers have setting. so we cannot solve it in common way, yes, @veksha ? |
Why was this closed? Don't you agree this is a good feature to have? |
Reopened. but I guess it is impossible to add, see my prev comment. |
I understand you don't know how to fix, but I see no reason for it to be impossible. I use the same LSP server in all the examples I gave ( |
VSCode:
Sublime:
Kate:
CudaText after typing
qa
: there's no autocomplete suggestion, I need to typequeryselectora
which is way slower.All these three editors use full-fuzzy for these autocomplete, but I guess the ideal would be to use the "smart fuzzy" implemented here, which is also used by VSCode for Command palette.
The text was updated successfully, but these errors were encountered: