-
Notifications
You must be signed in to change notification settings - Fork 26
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
Is client-side sorting really disabled? #56
Comments
After some investigation I found that company-lsp uses some cache for candidates and sorts them no matter what value is in |
Per specification, the server can specify This is more like a cquery bug if To check if |
Hey, thank you for your response!
so this field contains ordered alphanumeric string like (first 5 completion candidates)
|
Even if I set
|
Are the items you pasted in the same order as printed by Note that company-lsp explicitly tells company-mode do not sort the candidates again: Line 434 in dd7610a
And it uses lsp--sort-candidates internally which should sort by |
Yep, it is first 5 items our of 100, order is preserved. |
You're right, this piece of code from my emacs config was excess (and probably outdated):
Without it company-lsp started to work like a charm! |
Hi. I'm experiencing weird behaviour with
company-lsp-cache-candidates
variable.I'm using cquery + emacs-cquery + lsp-mode + company-lsp.
The thing is cquery sorts completion candidates itself and I don't want company to sort it, so I'm setting
company-lsp-cache-candidates
tonil
to disable caching and sorting (as documentation describes), but looks like completion candidates are sorted without respect to this parameter (company-lsp--on-completion
callslsp--sort-completions
without check ofcompany-lsp-cache-candidates
value). You can find more details in this pull request in the pre-last message jacobdufault/cquery#786 .So could you please help me with it? Thank you very much!
The text was updated successfully, but these errors were encountered: