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

Coi

by SublimeText ST4

Coi syntax for Sublime Text

Labels completions, language syntax, snippets

Details

Installs

  • Total 3
  • Win 2
  • Mac 0
  • Linux 1
Mar 16 Mar 15 Mar 14 Mar 13 Mar 12 Mar 11 Mar 10 Mar 9 Mar 8 Mar 7 Mar 6 Mar 5 Mar 4 Mar 3 Mar 2 Mar 1 Feb 28 Feb 27 Feb 26 Feb 25 Feb 24 Feb 23 Feb 22 Feb 21 Feb 20 Feb 19 Feb 18 Feb 17 Feb 16 Feb 15 Feb 14 Feb 13 Feb 12 Feb 11 Feb 10 Feb 9 Feb 8 Feb 7 Feb 6 Feb 5 Feb 4 Feb 3 Feb 2 Feb 1 Jan 31
Windows 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0
Mac 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Linux 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

Coi

Coi syntax definitions for Sublime Text based on its HTML and CSS syntax.

preview

Installation

Package Control

The easiest way to install is using Package Control. It's listed as Coi.

  1. Open Command Palette using ctrl+shift+P or menu item Tools → Command Palette...
  2. Choose Package Control: Install Package
  3. Find Coi and hit Enter

Manual Install

  1. Download appropriate Coi.sublime-package for your Sublime Text build.
  2. Copy it into Installed Packages directory

[!NOTE]

To find Installed Packages…

  1. call Menu > Preferences > Browse Packages..
  2. Navigate to parent folder

Troubleshooting

§1 Syntax Definition Parse Errors

Coi extends Sublime Text's HTML syntax definition.

If Coi syntax highlighting doesn't work and console displays syntax errors in Coi.sublime-syntax, please make sure to remove any out-dated syntax override.

Steps:

  1. call Menu > Preferences > Browse Packages..
  2. Look for HTML folder
  3. Remove it or at least delete any syntax definition in it.

§2 Styles are not correctly highlighted

Coi relies on CSS (source.css) to scope style blocks and inline style tag attributes.

Make sure to remove related out-dated syntax packages, which don't meet least compatibility requirements.

They can be identified by calling e.g. sublime.find_syntax_by_scope("source.css") in ST's console.