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

ESPHome

by SublimeText ST4

ESPHome YAML configuration file syntax for Sublime Text

Details

Installs

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