Skip to content

Repository files navigation

Sublime-GenericConfig

Sublime-GenericConfig adds syntax highlighting of the configuration files to Sublime Text 2 and Sublime Text 3.

It aims to provide generic highlighting for files which are not supported by other plugins (for example ini files, nginx config).

This plugin may be used for a wide range of configuration files because highlighting is based on common syntax constructions.

NOTE: 0.0.6 is last version for Sublime Text 2.

Supported constructions

  • One line comments (#, //, -- and ;)
  • Block comments (/* ... */)
  • Numbers, hex values, numbers with units (12M, 10kHz etc)
  • Color (#ccc, #12ccff etc)
  • Common constants (true/false, yes/no etc)
  • Strings (single quotes and double quoted)
  • Sections ([name], <name>, name { ... })
  • Key-value constructions (key = value, key: value, key value ...)
  • Variables ($name, %name, %name%, ${name} and few others)
  • Uppercase names (SOME_NAME)
  • URL-like strings (http://name.org, some://name:port/path)
  • RegEx-like strings (^...$)
  • Common operators (+, - etc)
  • Mime-like strings (image/gif, multipart/form-data etc)
  • Function call (name())

Usage

You can trigger GenericConfig manually for unknown files via the UI:

  • View -> Syntax -> Generic Config
  • View -> Syntax -> Open all with current extension as ... -> Generic Config

Or via settings:

To automatically associate GenericConfig with specific file extensions, create or edit the settings file at Packages/User/GenericConfig.sublime-settings (or any other supported location):

{
  "extensions":
  [
    "myext1",
    "another-ext",
    "mak",
    "mk"
  ]
}

In case of file type conflicts, you can override GenericConfig defaults by adding extensions to <syntax>.sublime-settings if you have any overlaps.

About

Generic highlighting of the configuration files for Sublime Text 2 and Sublime Text 3

Topics

Resources

Stars

43 stars

Watchers

2 watching

Forks

Releases

Packages

Contributors