ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Docs

Settings

The default settings can be viewed by accessing the Preferences > Package Settings > Package Control > Settings – Default menu. To ensure settings are not lost when the package is upgraded, make sure all edits are saved to Settings – User.

debug
If set to true, will print HTTP headers and other debug information to the Sublime Text console.
Default false
submit_usage
If installs, upgrades and removals should be logged to the reporting URL. This data will be used to power the community package listing and will be displayed in aggregate only. No user-identifiable information is sent, just the: package name, operation, package version, package control version, sublime version and sublime platform.
Default yes
submit_url
Where the usage information should be sent to.
Default "https://sublime.wbond.net/submit"
installed_packages
A list of packages that have been installed. Package Control will automatically install any packages in this list that are not currently installed, allowing this to be used for sharing package lists with other users. This setting is only tracked in Settings – User.
Default []
channels
A list of URLs that each contain a JSON file with a list of repositories. The repositories from these channels are placed in order after the repositories from the repositories setting.
Default ["https://sublime.wbond.net/channel.json"]
repositories
A list of URLs that contain a packages JSON file. These repositories are placed in order before repositories from the repository_channels setting.
Default []
install_prereleases
Install pre-release versions of packages. If this is false, versions under 1.0.0 will still be installed. Only packages using the SemVer -prerelease suffixes will be ignored.
Default false
package_name_map
This helps solve naming issues where a repository it not named the same as the package should be. This is primarily only useful for GitHub and BitBucket repositories. This mapping will override the mapping that is retrieved from the repository channels.
Default {}
auto_upgrade
If packages installed via Package Control should be checked for updates when Sublime Text starts. Updates will be automatically installed.
Default true
auto_upgrade_frequency
The number of hours to wait before trying to auto upgrade packages again.
Default 6
auto_upgrade_ignore
Packages to exclude from the auto upgrade functionality.
Default []
install_missing
If set to false, will not automatically install packages from the installed_packages setting that are not present on the current machine. This is really only useful if you don’t want Sublime Text to connect to the internet without explicitly requesting it. In that case you’ll want to set auto_upgrade to false also.
Default true
timeout
The HTTP timeout (in seconds) to use when downloading channels, repositories and packages.
Default 30
cache_length
The number of seconds to cache channel and repository metadata for.
Default 300
http_cache
If HTTP request responses should be cached.
Default true
http_cache_length
Number of seconds to cache HTTP responses for.
Default 604800
http_proxy
The proxy to use for HTTP requests. Should be in the form domainname:port or ip:port.
Default ""
https_proxy
The proxy to use for HTTPS requests. If http_proxy is set and this settings is not, the value from http_proxy will be used. If set to false, then http_proxy will not be inherited. Should be in the form domainname:port or ip:port.
Default ""
proxy_username
The username to use for proxy authentication.
Default ""
proxy_password
The password to use for proxy authentication.
Default ""
user_agent
The user agent used by the various downloaders.
Default "Sublime Package Control v{version.number}"
git_binary
The path to git, when using a git repository to track a package. When an empty string, Package Control will look in default locations for the current OS.
Default ""
git_update_command
The parameters passed to git to update a package. The remote and branch will be automatically determined.
Default ["pull", "--ff", "--commit"]
hg_binary
The path to hg, when using an hg repository to track a package. When an empty string, Package Control will look in default locations for the current OS.
Default ""
hg_update_command
The parameters to pass to hg to update a package. Will always pull from the URL named default.
Default ["pull", "--update"]
ignore_vcs_packages
If git and hg repositories should be ignored when trying to update packages.
Default false
openssl_binary
Only necessary if openssl can not be found and the Grab CA Certs command is run.
Default ""
dirs_to_ignore
A list of folders to ignore when creating a .sublime-package file.
Default [".hg", ".git", ".svn", "_darcs", "CVS"]
files_to_ignore
A list of file glob patterns to ignore when creating a .sublime-package file by the Create Package command.
Default [".hgignore", ".gitignore", ".bzrignore", "*.pyc", "*.sublime-project", "*.sublime-workspace", "*.tmTheme.cache"]
files_to_include
A list of file glob patterns to include when creating a .sublime-package file by the Create Package command. This overrides files_to_ignore.
Default []
files_to_ignore_binary
A list of file glob patterns to ignore when creating a .sublime-package file by the Create Binary Package command.
Default [".hgignore", ".gitignore", ".bzrignore", "*.py", "*.sublime-project", "*.sublime-workspace", "*.tmTheme.cache"]
files_to_include_binary
A list of file glob patterns to include when creating a .sublime-package file by the Create Binary Package command. This overrides files_to_ignore_binary.
Default ["__init__.py"]
package_destination
The folder to copy a newly created package to. Default to the user’s Desktop if blank. Setting this destination to the Installed Packages directory will cause your source code changes to be overwritten when Sublime Text restarts!
Default ""
certs

A list of CA cert information for the purpose of providing a secure way to download packages. A default list is provided with Package Control, but then the default repository channel provides updates to the list. It is also possible to add your own entries for custom download locations, or for supporting your local proxy server.

To add your own, be sure to copy the JSON object below and then add your custom entries. The key in the JSON object is the domain the cert applies to. The value is an array with two elements, the first being an identifier for the cert, and the second being a location to copy the cert from. The identifier is used to ensure that Package Control has a copy of the latest version of the cert in its certs/ folder. The location can be either an absolute file path on your local machine, or a URL to download it from.

To create a CA cert that is ensured to be present no matter what domain is being accessed (such as for a proxy server), set the domain name to *, like in the example on the next line:

"*": ["my_proxy_cert", "/file/path/to/proxy/ca_certs"]

This ca cert needs to live somewhere on your machine permanently so that it can be re-added to the ca-bundle.crt file that is provided with each Package Control upgrade.

Default
{
    "api.bitbucket.org": ["d867a7b2aecc46f9c31afc4f2f50de05", ""],
    "api.github.com": ["1c5282418e2cb4989cd6beddcdbab0b5", ""],
    "bitbucket.org": ["897abe0b41fd2f64e9e2e351cbc36d76", ""],
    "nodeload.github.com": ["1c5282418e2cb4989cd6beddcdbab0b5", ""],
    "raw.github.com": ["1c5282418e2cb4989cd6beddcdbab0b5", ""],
    "sublime.wbond.net": ["7f4f8622b4fd001c7f648e09aae7edaa", ""]
}