You can; there’s a setting for that:
// List any packages to ignore here. When removing entries from this list,
// a restart may be required if the package contains plugins.
Packages that are ignored are, as the name suggests, ignored. Nothing that they contain will be visible to Sublime. Note that in the case of Python and C++ (among other packages) that also makes the syntax definitions vanish away too.
If you just want to get rid of snippets and you’re using ST
4, you don’t have to do either of those things because there’s a dedicated setting for this already:
// A list of wildcard patterns specifying which snippet files to ignore.
// For example, to ignore all the default C++ snippets, set this to
As you might expect (and have seen), when Sublime updates it updates it’s installation folder completely; that folder should be a “hands off” folder.
If you want to entirely remove a package, add it to the list of
ignored_packages in your user preferences, and it’s contents will be wholly ignored whether it’s on disk or not.
You can also mask shipped packages in a “safer” way by creating an empty
.zip file, renaming it to the appropriate package (say
C++.sublime-package) and then dropping it into the
Installed Packages folder. If a
sublime-package file with the same name appears in both the install folder and
Installed Packages, sublime will use the
Installed Packages version.
Here “safer” is in the mysterious quotes because in doing this, you’re making sure for all time that no matter what happens in your copy of Sublime or how many times you reinstall it, you’ll never have access to the shipped package again unless you remember that you did this. You will receive 0 warning one way or the other. Confusion will likely ensue at some point in the future.
Hence, the settings are the better way to go.