Sublime Forum

Autocomplete on exact matches

#1

When you’ve typed something that is an exact match to an auto-complete suggestion, sometimes the suggestion switches to a less-exact match. As an example, in a fresh instance of Sublime, create a Python file with this:

some_truthy_value = 42
foo = True
assert foo ==

…and then, after the equality check at the end, type “True”. For the first three characters, the auto-complete suggestion list will be:

True
some_truthy_value

…but as soon as you finish typing the full word, the suggestion list reduces to just “some_truthy_value”, and hitting enter (as would come naturally in an assert statement like this) will then get you the wrong thing.

If feels like if there is an exact match for what you just typed, that should stay on the top of the suggestion list. Is there a way to get this behavior?

2 Likes

#2

Exact matching completions are removed due to https://github.com/sublimehq/sublime_text/issues/3434

It also helps to reduce duplicate completion items.
see: https://github.com/sublimehq/sublime_text/issues/3280

0 Likes

#3

Ah, thanks for the context! Filed a bug and will see where that goes. https://github.com/sublimehq/sublime_text/issues/4810

0 Likes

#4

I highly upvote this. Quite often I’m typing in all the letters of a word in lowercase, and expect the completion of suggest the correct camelCase instead. It bite me so many times already :frowning:

0 Likes

#5

Yep, this one is killing me too. I think those changes from 3434/3280 need some more thought…

0 Likes