-
Notifications
You must be signed in to change notification settings - Fork 9
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
Disable auto complete #118
Comments
You can do this in your {
"disabled_capabilities": {
"completionProvider": true,
},
} |
Oh, really... Thanks, that helped. |
Either way makes sense to me. Maybe someone doesn't want ST's autocompletion (since it's provided by "guessing") but wants to keep LSP's. |
Maybe it would be true if not the next problem i met. Plugin turns on default Sublime's autocomplete for JSON files! Autocomplete popup keep showing, but now it suggests me words that exists on other places inside opened file. |
Not sure what you mean. |
No, autocompletion turns on no matter what value this option has, just if a plugin is installed and enabled. Setting |
Makes sense to me. |
My first thought is that |
This looks like this core issue: sublimehq/sublime_text#4240 Nothing to track in this repo so closing. |
A little background: I'm a real, i mean, 100% hater of autocomplete and all that popups over my code and intercepts keyboard controls. So I decided to cut off this feature at the root a years ago by setting
"auto_complete": false
in general Sublime's settings.But today I have installed LSP-json for fast linting, highlighting erorrs, hints, etc. in my JSON files. But not for autocomplete. I never asked for this.
The problem is, even with
"auto_complete": false
, when that plugin enabled, Sublime showing me autocomplete popup at least when I starting to write property name.And i don't know how to disable this behavior. Maybe I missing some option in plugin's configuration, but I rather guess it's some kind of a bug. Because I have installed a lot of plugins in my developer's life, and no one of them ever showed me an autocomplete interface with aforementioned option disabled.
If it is, after all, somehow, not a bug but a feature, I have a question "why?" and asking for help to disable it.
The text was updated successfully, but these errors were encountered: