How do I turn this javascript autocomplete stuff off easily?

[UltimateCodeWarrior]

Description of the bug

Some sort of auto complete when editing javascript files is really getting to me.

When I went to the Sublime Text Preferences Settings, there was some super WONKY text file that came up and said "auto_complete":true, but it wouldn't allow me to edit and save it? Why bother even showing it if you can't do nothing with it? Really? Why wasn't there just some check box to turn in off and on like the rest of the world would do?

Steps to reproduce

Just update latest version and try to edit a javscript file, like create a const constructor and start trying to edit it without having that blasted popup appear.

Expected behavior

When that popup appears, would be nice to have a button in the popup itself that says "Disable this, never show it again."

Actual behavior

Just as I said it would happen.

Sublime Text build number

Build 4169

Operating system & version

Monterey 12.7.2

(Linux) Desktop environment and/or window manager

Mac

Additional information

No response

OpenGL context information

No response

[BenjaminSchaaf]

You can turn off auto-completions using the "auto_complete" setting. In the left hand pane of our settings are the defaults and on the right side are your overrides. Adding "auto_complete": false, to the right hand side is likely what you're looking for.

[UltimateCodeWarrior]

Hi Benjamin,
I tried that, saved, closed out and came back, still the issue persists.

[BenjaminSchaaf]

Does it happen in safe mode? It's likely you've installed a plugin that's causing that behavior.

[UltimateCodeWarrior]

I deleted these Package folders from sublime text to acid wash out anything that might be lingering....but low and behold sublime text clawed them back into the package folder. How do I get rid of this stuff for good?

[UltimateCodeWarrior]

Wouldn't it have made sense to have some way to delete a package from within Sublime, but instead I get this misdirection :

[jfcherng]

Fwiw, "Package Control" is a "personal" plugin and SublimeHQ has no control over it.

You can type "Remove Package" in command palette to remove a plugin/package.

[BenjaminSchaaf]

Documentation for reverting to a freshly installed state is found here: https://www.sublimetext.com/docs/revert.html. Note that safe mode effectively does the same thing without touching your files so that's the first thing to try.

Removing a package is found either in the command palette or under Preferences > Package Control.

[UltimateCodeWarrior]

I think there should be some sort of master auto_complete kill switch that all "Plugins" aka "Packages" are tethered to so that if you throw that circuit breaker, it's ability to manifest itself has been hamstrung by the Sublime Text app. All this willy-nilly wild wild west stuff which is hard to trace and control really messes up the user experience. I had to manually go in and blow that stuff out of a text file before the Sublime app wouldn't re-pull it down from the internet.

IMHO, I think enable / disable the plugins/packages should just be a checkbox in a dropdown so that a user can quickly figure out which one is the wayward culprit. A delete button should be right next to each of these with a confirmation, and then once you press "Destroy It", it's gone for good. Maybe with a little popup that you can send a writeup to the author of the plugin why you had to toast it so they can go back to the drawing board and do some continuous improvements.

[deathaxe]

OP's screenshot shows snippets, shipped with default syntax packages. They can be disabled by "ignored_snippets": ["JavaScript/*"],