-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
Command palette's camel case matching does not work for non ASCII characters #4691
Comments
@mysticatea ran into this issue too: |
@bpasero assigning to you since this is quick box related. Marking as candidate since we should look into fixing this for 1.0. Let me know if there is something I can do from the translation side. |
Looked into this and I think the issue is not about finding Japanese input in general but rather how the filtering works in the command palette. There are different matchers being used and one of them is a camel case matcher that would match for a given input of Matching on camel case in the command palette is questionable and should probably be revisited. I quickly checked to use another matcher approach with fully fuzzy matching (similar to files) and could not reproduce the issue there. However, changing our filtering for commands like that can have quite an impact and we also need to revisit the sorting in that case. I would not do this for GA, but @egamma and @chrisdias should speak up. |
makes sense |
Related: #1964 |
Another user who wants either English back or supports English in addition to their native language. #4785
|
I changed our matching in the commands quick open to also match non-ascii beginning of words. This is not yet fuzzy matching, but returns a lot more results that make sense. Basically the matching is now supporting any beginning of a word (e.g. "gp" matches "Git: Pull" as well as "g p" does). |
A fix has landed in insiders. You can give it a try from our insiders release today: http://code.visualstudio.com/Download#insiders Happy for feedback! |
From @espresso3389 in #4679:
Is there an optimization to not recheck characters if the last character is replaced? While not being shown here, Japanese IMEs can also transforms multiple Japanese characters into an even smaller number of characters, by going from English -> Kana -> Kanji.
The text was updated successfully, but these errors were encountered: