-
Notifications
You must be signed in to change notification settings - Fork 93
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
Provide case-insensitive completion #405
Provide case-insensitive completion #405
Conversation
It may be desired for the exact matches to show first. Though it may need some moderate refactoring. |
I don't know how other editors handle the order, vscode already does it by choosing the exact match first. |
How about the following situation?
What do |
Thank you for working on it. Didn't have the time to test it. By the way, am I correct that for
|
Currently, no. I only switch from
Given the returned completion items, it is then up to the editor to determine how to present these items. |
I am a bit confused why for example Perhaps it was because the list was generated by the server when |
When /**
* This list it not complete. Further typing should result in recomputing
* this list.
*/
isIncomplete: boolean; If the token at cursor is already |
Thank you for the explanation. Totally forgot this setting. It makes total sense. |
Closes #401.
This PR uses
grep(ignore.case=TRUE)
to provide case-insensitive and partial matching completion items to replace the current case-sensitive, exact-matching-from-start filtering.