Allow inhibiting word completions based on a scope selector

[FichteFoll]

Problem description

When offering a list of exclusive completions via .sublime-completions files, there is currently no way to prevent buffer completions from being offered. The only way to do that would be to create a plugin whose sole purpose is to return sublime.INHIBIT_WORD_COMPLETIONS for certain scope selectors.

Preferred solution

A new key inside .sublime-completions files (next to "scope" and "completions") to inhibit word completions when the list you offer is exclusive. E.g.:

{
    "scope": "meta.kind.sublime-completions",

    "inhibit_word_completions": true,
    "completions": [
        {
            "trigger": "ambiguous",
            "details": "Ambiguous",
            "kind": ["type", "k", "kind"],
        },
    ]
}

Alternatives

A new key for .tmPreferences (or some new format 😉) to inhibit word completions.

Additional Information (optional)

This it what it currently looks like for a list of exclusive completions. (Yes, this completions file is for completions files themselves.)

[FichteFoll]

I just tried to work around this limitation using an on_query_completions hook that would return [], sublime.INHIBIT_WORD_COMPLETIONS for scopes that I also define completions for through sublime-completions files, but had to realize that the flag isn't picked up unless I also return at least one completion at the same time. An empty completion (with an empty trigger) doesn't work either.