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

ESPHome

by SublimeText ST4

ESPHome YAML configuration file syntax for Sublime Text

Labels language syntax

Details

Installs

  • Total 44
  • Win 15
  • Mac 19
  • Linux 10
Aug 26 Aug 25 Aug 24 Aug 23 Aug 22 Aug 21 Aug 20 Aug 19 Aug 18 Aug 17 Aug 16 Aug 15 Aug 14 Aug 13 Aug 12 Aug 11 Aug 10 Aug 9 Aug 8 Aug 7 Aug 6 Aug 5 Aug 4 Aug 3 Aug 2 Aug 1 Jul 31 Jul 30 Jul 29 Jul 28 Jul 27 Jul 26 Jul 25 Jul 24 Jul 23 Jul 22 Jul 21 Jul 20 Jul 19 Jul 18 Jul 17 Jul 16 Jul 15 Jul 14 Jul 13
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 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Mac 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Linux 0 0 1 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

Readme

Source
raw.​githubusercontent.​com

ESPHome

ESPHome YAML configuration file syntax for Sublime Text based on its YAML syntax.

preview

Installation

Package Control

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

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

Manual Install

  1. Download appropriate ESPHome.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

[!WARNING]

Manually installed packages are not automatically updated by Package Control.

Usage

To apply the syntax, select YAML (esphome) from the Command Palette or from the syntax selector in the status bar.

Since ESPHome configuration files use the .yml/.yaml extension and do not differ much from standard YAML files, there is no easy way to automatically assign it to all ESPHome configuration files (unless you want to use this syntax for all YAML files, which could introduce its own problems). Therefore, it is recommended to use the ApplySyntax or AutoSetSyntax package to assign this syntax based on the file path - most likely on a per-project basis since there is nothing inherently unique about the file names or paths of these configuration files.