Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Tools to ease the creation of snippets, syntax definitions, etc. for Sublime Text.
Python JavaScript PowerShell
Failed to load latest commit information.
Lib OutputPanel.write_line parameter now optional
Snippets Rename the snippets directory for JSON Syntax Definitions
Support Remove references to deleted commands
Syntax Definitions Remove incomplete comment matching for (?x) groups
bin improve completions syntax def; minor changes to scripts
fileconv Don't eat any exceptions when loading or dumping
messages Changelog for 1.0.7
tests Remove setup.py
.gitignore gitignore
.hgignore add command to convert from tmLanguage to JSON-tmLanguage
.hgtags Added tag 0.5.0 for changeset 2096aabefbca
AAA.py Make imports work when in .sublime-package
AUTHORS.txt added notification messages; admin stuff
CONTRIBUTORS.txt added notification messages; admin stuff
LICENSE.txt add license
README.rst Update README with better explanations
build_sys_dev.py Update plugin files to work with ST3
commands_file_dev.py Update plugin files to work with ST3
completions_dev.py Update plugin files to work with ST3
file_conversion.py Delay saving to fix "dirty" indicator
manifest.in Revised manifest.in.
messages.json Changelog for 1.0.7
scope_data.py Add some punctuation scopes for completion
settings_dev.py Update plugin files to work with ST3
snippet_dev.py Update plugin files to work with ST3
sublime_inspect.py Update plugin files to work with ST3
syntax_def_dev.py Don't check if the prev character was a comment

README.rst

AAAPackageDev

Overview

AAAPackageDev is a Sublime Text 2 and 3 package that helps create and edit syntax definitions, snippets, completions files, build systems and other Sublime Text extension files.

The general workflow looks like this:

  • run new_* command (new_raw_snippet, new_completions, new_yaml_syntax_def...)
  • edit file (with specific snippets, completions, higlighting, build systems...)
  • save file

AAAPackageDev commands are typically accessible through the Command Palette (Ctrl+Shift+P).

Getting Started

  1. After installing Package Control, use the Command Palette (Ctrl+Shift+P) to select Install Package and then search for AAAPackageDev.
  2. Access commands from Tools | Packages | Package Development or the Command Palette.

Alternatively, download and install AAAPackageDev manually. (See installation instructions for .sublime-package files.)

Syntax Definition Development

In AAAPackageDev, syntax definitions are written in YAML (previously JSON). Sublime Text uses Plist XML files with the .tmLanguage extensions, so they need to be converted before use if you want to modify an already existing syntax definition.

Creating a New Syntax Definition

  1. Create new template (through Tools | Packages | Package Development) or the Command Palette
  2. Select Convert to ... build system from Tools | Build System or leave as Automatic
  3. Press F7 or Ctrl+B

Other included resources for syntax definition development:

  • Syntax highlighting, including Oniguruma regular expressions
  • A command to rearrange unsorted (or alphabetically sorted) syntax definitions in YAML. See the command's detailed docstring in file_conversion.py for parameters and more.
  • Static and dynamic completions
    • All basic keys like name and captures.
    • Numbers will automatically be turned into capture groups. This means that typing 4<tab> results in '4': {name: }.
    • Scope names are completed as per TextMate naming conventions, with the last section being the base scope name.
    • Includes are completed as per defined repository keys.

For a good example definition (as to why using YAML is way better than the plain Plist), see the syntax definition for YAML-tmLanguage files: Sublime Text Syntax Def (YAML).YAML-tmLanguage

Editing Existing Syntax Definitions

You can convert JSON or Plist files to YAML any time (using the Convert to... build system), but for convenience AAAPackageDev provides a migration command that takes care of all that, and more.

This is highly recommended! Running Convert to YAML and Rearrange Syntax Definition will convert the JSON or Plist syntax definition at hand into YAML and additioally prettify it. To ensure proper markup of the syntax definition, explicitly convert indentation to spaces using the Indentation: Convert to Spaces command before converting.

You can also run the command Rearrange YAML Syntax Definition from the Command Palette manually to sort all lines reasonably, turn strings into their block representation, remove redundant mapping symbols and insert line breaks where they're useful.

"Convert to..." Build System

The "Convert to..." build system can interchangably convert JSON, YAML and Plist files. The source format is automatically detected, as long as it's possible, and will then prompt you for the target file's format. While this is primarily used for syntax definition it can be used for any file.

It will also adjust the target file's extension, following a few rules:

  • I am json.json is parsed into I am json.plist (or .yaml).
  • I am json.JSON-propertyList is parsed into I am json.propertyList.

You can override both, the target format and the extension, by providing an options dict in one of the first three lines of a file. An options dict is indicated by a line comment starting with [PackageDev]. Everything to the end of the line commend (or --> for Plist) will then be treated as a YAML dict.

Currently supported options are: * target_format, options: plist, yaml and json * ext, without leading .

Example (YAML): # [PackageDev] target_format: plist, ext: tmLanguage

Note: The JSON parser can handle JavaScript-like // and `` /* */`` comments. For obvious reasons, comments are not preserved.

Build System Development

  • Syntax definition for .build-system files.

Key Map Development

  • Syntax definition for .sublime-keymap files.
  • Completions
  • Snippets

Snippet Development

AAAPackageDev provides a means to edit snippets using snippets. These snippets are called raw snippets. You can use snippets and snippet-like syntax in many files, but if you want to create .sublime-snippet files, you need to convert raw snippets first. This converion is done with a command.

Inside AAAPackageDev/Support you will find a .sublime-keymap file. The key bindings in it are included for reference. If you want them to work, you need to copy the contents over to your personal .sublime-keymap file under Packages/User.

Creating Snippets

  1. Create new raw snippet with included commands (Tools | Packages | Package Development or Command Palette)
  2. Edit snippet
  3. If needed, convert to .sublime-snippet with included command

You can use raw snippets directly in some files, like .sublime-completions files.

Completions Development

  • Syntax definition for .sublime-completions files
  • Snippets

You can use raw snippets directly in the contents element of a trigger-based completion.

Settings File Development

  • Syntax definition for .sublime-settings files
  • Snippets

About Snippets in AAAPackageDev

The AAAPackageDev/Snippets folder contains many snippets for all kinds of development mentioned above. These snippets follow memorable rules to make their use easy.

The snippets used more often have short tab triggers like f (field), c (completion), k (key binding), etc. In cases where increasingly complex items of a similar kind might exist (numbered fields, fields with place holders and fields with substitutions in the case of snippets), their tab triggers will consist in a repeated character, like f, ff and fff.

As a rule of thumb, the more complex the snippet, the longer its tab trigger.

Also, i (for item) is often a generic synonym for the most common snippet in a type of file. In such cases, ii and even longer tab triggers might work too for consistency.

Sublime Library

AAAPackageDev includes sublime_lib, a Python package with utilities for plugin developers. Once AAAPackageDev is installed, sublime_lib will be added to Python's PATH and importable from any other plugin.

Deprecated: Do not use this library in production anymore because it will be removed in a future release and probably turned into a Package Control dependency instead.

Something went wrong with that request. Please try again.