-
Notifications
You must be signed in to change notification settings - Fork 40
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
Autocomplete suggestions not matched correctly in 4134 #5437
Comments
I can confirm this is happening for PHP as well. |
|
Shouln't have any impact on static completions from *.sublime-completions file. Note: I was able to reproduce this behavior in SAFE MODE with plain PHP completions. Typing |
Will the next stable build be released with this regression? |
As mentioned in #5431, this appears to be fixed in 4138. (have also verified that with my test code) |
I can confirm that this has been fixed for HTML and seems to be working correctly for PHP too. |
Fixed in Build 4138 |
Description of the bug
For example, typing "$v" doesn't automatically select the "$var" completion but prefers "var_dump".
Steps to reproduce
Expected behavior
The "$var" completion is selected like in the build 4131:
Actual behavior
The "var_dump" completion is selected. Seems like "$" is not considered when matching completions (it's also not highlighted):
Sublime Text build number
4134
Operating system & version
macOS 12.4
(Linux) Desktop environment and/or window manager
No response
Additional information
Might be related to the fix made for #4855.
Note that in both 4131 and 4134 builds the
prefix
argument toon_query_completions
is an empty string when typing the initial$
. Feels a bit weird but regardless of that, it has worked before.Also note that (even if it didn't happen before either) filtering out the
var_dump
completely would probably make more sense if$
is used for matching as "var_dump" doesn't contain the$
character.OpenGL context information
No response
The text was updated successfully, but these errors were encountered: