Packages 0,0,0,2,3,0,1

2 years after

Sublime Packages

These packages are developed against the latest Sublime Text 3 Dev Build. Bugs may exist on older builds, and the format used is not compatible with builds older than 3092.

Installation

If you want to make changes to these packages and test them locally, fork this repository and then symlink the changed packages into your Packages folder.

Replace Python in the following commands with the name of the syntax to install.

OS X

$ git clone https://github.com/sublimehq/Packages.git
$ ln -s `pwd`/Packages/Python ~/Library/Application\ Support/Sublime\ Text\ 3/Packages/

Linux

$ git clone https://github.com/sublimehq/Packages.git
$ ln -s `pwd`/Packages/Python ~/.config/sublime-text-3/Packages/

Windows

On Windows, you can use directory junctions instead of symlinks (symlinks require administrative rights; directory junctions don't):

# Using PowerShell
PS> git clone https://github.com/sublimehq/Packages.git
PS> cmd /c mklink /J "$env:APPDATA/Sublime Text 3/Packages/Python" (convert-path ./Packages/Python)

Alternatively, download the portable version, and clone this repository directly as a subdirectory of the Data folder.


After you've finished, keep in mind that you're now overriding a default package. When Sublime Text updates to a new version, you'll run the risk of having an out-of-date package unless you pull the latest changes from this repository.

Pull Requests

Pull requests should:

  1. Start with the name of the package in square brackets, e.g. [XML].
  2. Be as small and self-contained as is reasonable. Smaller changes are quicker to review.
  3. Include a new, or enhanced, syntax test when changing a .sublime-syntax file.
  4. Have multiple syntax tests and a set of performance measurements (old vs. new) when making significant changes.

New Packages

Pull requests for new packages won't be accepted at this stage, as new packages can cause issues for users who have a package with the same name installed via Package Control. There are some planned changes that will address this in the future.

Complex plugins such as auto complete systems and linters should generally be in a stand-alone package, rather than included in the default set of packages.

Missing Packages

This repository only contains syntax-definition-focused packages. Notably, packages such as Default and Theme - Default are not included.

Related Repositories

termux-packages

termux-packages

Android terminal emulator and Linux environment - packages repository. ...

void-packages

void-packages

The XBPS source packages collection ...

platform-install-packages

platform-install-packages

Official deployment packages to install the Kaltura platform on a server or clus ...

awesome-atom-packages

awesome-atom-packages

:package: Some Useful Atom Packages for Web Developers ! ...

rumprun-packages

rumprun-packages

Ready-made packages of software for running on the Rumprun unikernel ...


Top Contributors

wbond djspiewak keith-hall Briles FichteFoll randy3k Clamsax sublimehq jskinner ccampbell r-stein kleinfreund tmichel duncan3dc gerardroche aziz StrangeNoises jfcherng guillermooo michaelblyons gwenzek jbrooksuk SirNickolas vladdeSV jcberquist urraka LoneBoco poke ptcong tobiasdiez

Releases

-   v3123 zip tar
-   v3122 zip tar
-   v3121 zip tar
-   v3120 zip tar
-   v3119 zip tar
-   v3118 zip tar
-   v3117 zip tar
-   v3116 zip tar
-   v3115 zip tar
-   v3114 zip tar
-   v3113 zip tar
-   v3112 zip tar
-   v3111 zip tar
-   v3110 zip tar
-   v3109 zip tar
-   v3108 zip tar
-   v3107 zip tar
-   v3106 zip tar
-   v3105 zip tar
-   v3104 zip tar
-   v3103 zip tar
-   v3102 zip tar
-   v3101 zip tar
-   v3100 zip tar
-   v3099 zip tar
-   v3098 zip tar
-   v3097 zip tar
-   v3096 zip tar