Package Control Proxy
Settings – Package Control
Docs
The default settings can be viewed by accessing the
menu. To ensure settings are not lost when the package is upgraded,
make sure all edits are saved to.
debug
If set to true, will print HTTP headers and other debug
information to the Sublime Text console.
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.
submit_url
Where the usage information should be sent to.
Default”
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.
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[“]
repositories
A list of URLs that contain a packages JSON file. These repositories
are placed in order before repositories from the
repository_channels setting.
install_prereleases
A list of packages to install pre-release versions for. Versions
under 1. 0. 0 are not considered pre-release; only those using the
SemVer -prerelease suffixes will be ignored if the package
is not in this list.
package_name_map
This helps solve naming issues where a repository is 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.
auto_upgrade
If packages installed via Package Control should be checked for
updates when Sublime Text starts. Updates will be automatically
installed.
auto_upgrade_frequency
The number of hours to wait before trying to auto upgrade
packages again.
auto_upgrade_ignore
Packages to exclude from the auto upgrade functionality.
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.
timeout
The HTTP timeout (in seconds) to use when downloading channels,
repositories and packages.
cache_length
The number of seconds to cache channel and repository metadata for.
_cache
If HTTP request responses should be cached.
_cache_length
Number of seconds to cache HTTP responses for.
_proxy
The proxy to use for HTTP requests. Should be in the form domainname:port
or ip:port.
The proxy to use for HTTPS requests. If _proxy is set
and this settings is not, the value from _proxy will
be used. If set to false, then _proxy will
not be inherited. Should be in the form domainname:port
proxy_username
The username to use for proxy authentication.
proxy_password
The password to use for proxy authentication.
user_agent
The user agent used by the various downloaders.
Default”Package Control v{}”
git_binary
Custom path(s) to git binary for when it can’t be
automatically found on the system and a package includes a
metadata directory. Supports more than one path to
allow users to sync settings across operating systems.
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
Custom path(s) to hg binary for when it can’t be
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.
downloader_precedence
The downloader backends that should be used for HTTP(S)
requests, split by operating system to allow for configuration
to be shared.
Valid options include: “urllib”, “curl”,
“wget”, (Windows-only) “wininet”.
This setting allows Windows users to bypass wininet and use
urllib instead if their machine or network presents trouble to
wininet. Some Mac and Linux users have also reported better
luck with certain proxies using curl or wget instead of urllib.
The “curl” and “wget” options require the
command line curl or wget program installed
and present in the PATH.
Default{
“windows”: [“wininet”],
“osx”: [“urllib”],
“linux”: [“urllib”, “curl”, “wget”]}
dirs_to_ignore
A list of folders to ignore when creating a. sublime-package
file.
Default[“”, “”, “”, “_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”, “*”, “*. sublime-project”, “*. sublime-workspace”, “*. “]
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.
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!
package_profiles
A way to create different packaging profiles for different types of
package releases, such as for different platforms or binary-only
releases.
The key of the object will be the profile name and a list of them will
be presenting when running the “Create Package File” command. The
profile “Default” will use the top-level version on the following
settings:
“dirs_to_ignore”
“files_to_ignore”
“files_to_include”
“package_destination”
If a profile does not include one of those three settings, it will fall
back to the top-level settings.
“Binaries Only”: {
// Exclude all files, but consequently include all files
“files_to_ignore”: [
“*”, “. bzrignore”,
“*. “],
// Include so Sublime Text will load the package
“files_to_include”: [
“”]}}
enable_tests
Enable the ability to run the tests – this is only for development.
sublime text 3 package control install – Stack Overflow
Setting Up Package Control to Work from Behind a Proxy Server
You will need to setup your proxy server in the Package Control settings.
Copy and paste the code below into a file called Package blime-settings which must be saved in your User config folder. That is the same folder as your USER blime-settings file is saved in. The Data Directory states where this is on your operating system. i. e.
Windows:%APPDATA%\Sublime Text 3\Packages\User\Package blime-settings
OS X: ~/Library/Application Support/Sublime Text 3/Packages/User/Package blime-settings
Linux: ~/ blime-settings
Clearly you must add the domain and port and your user name and password in the relevant fields below. The proxy should be in the form: proxyserver:port. e. g.
{
“_proxy”: “”,
“proxy_username”: “mynameis”,
“proxy_password”: “mypassis”, }
See also: Package Control Settings
// An HTTP proxy server to use for requests. Not normally used on Windows
// since the system proxy configuration is utilized via WinINet. However,
// if WinINet is not working properly, this will be used by the Urllib
// downloader, which acts as a fallback.
// An HTTPS proxy server to use for requests – this will inherit from
// _proxy if it is set to “” or null and _proxy has a value. You
// can set this to false to prevent inheriting from _proxy. Not
// normally used on Windows since the system proxy configuration is
// utilized via WinINet. However, if WinINet is not working properly, this
// will be used by the Urllib downloader, which acts as a fallback.
// Username and password for both _proxy and _proxy. May be used
// with WinINet to set credentials for system-level proxy config.
“proxy_username”: “”,
“proxy_password”: “”, }
Install and Use Package Control Behind Proxy – Laur IVAN
Skip to contentTL;DR: Install Package Control manually. Add the proxy settings to the configuration file as described in step 2 I’ve had to install Sublime Text 3 again on a new computer. Package control didn’t want to install due to my proxy settings (I was getting a 407 error code – Proxy authentification required). I managed to do it with two simple steps:Install Package Control manually. At the time of writing this post, the process is simple:Click the Preferences > Browse Packages… menuBrowse up a folder and then into the Installed Packages/ folderDownload Package blime-package and copy it into the Installed Packages/ directoryRestart Sublime TextSet the proxy coordinates in the settings:Click the Preferences > Browse Packages… menuEnter the User directoryOpen Package blime-settingsAdd the following JSON entries to the file:_proxy – your proxy address/port (x. x. x:port)proxy_username – the user name for authenticationproxy_password – the passwordNote: Your proxy password will be stored in plain text so you might want to set up file permissions…A little experiment:
