Sublime Forum

Messed-up completions in sublime syntax scopes

#1

I’ve been a while away from Sublime. Before, I remember that developing syntaxes, and specifically adding scopes to rules was made easy by completions. For examply typing scope: keyword. would give me as completion just the relevant standard specifiers of the keyword scope (e.g. control, definition, etc). However, now that I’m coming back to Sublime, this is no longer the case, now it gives me just any word I’ve used in the current file. (this is using the syntax provided by PackageDev).

Is anyone else experiencing this? How can I fix it?
Thank you in advance.

Edit: maybe a related issue: before, when putting the cared over a capture index, the corresponding group in the match’s regex would be highlighted. Now this is no longer the case.

0 Likes
#2

It sounds like this issue is related to the PackageDev package, not to core Sublime functionality.

Is it possible that PackageDev is not currently installed, or that it is ignored?

0 Likes
#3

I’m pretty much assuming it is some weird interaction between packages or between the app and a package, yes, and as to your question, I can see the PackageDev-related menu items so that should be sufficient signal of it being installed and activated, right?

Is there any way to ‘validate the integrity’ of an installed package?

0 Likes
#4

The easiest way would be to uninstall and reinstall the package. You can also check the console when Sublime starts to see if there are any error messages related to PackageDev.

2 Likes