{{event_type}} variable

[Taitava]

I'm not sure if I've already written about this idea. Maybe not, as I didn't find anything relevant when searching for event type.

If multiple events are enabled for a shell command, it could be useful to know which event actually executed it.

• {{event_type}} gives an exact identifier for the triggered event.
• {{event_type:category}} gives a "group" name for the event. Multiple events can share the same category.

Event name in UI	Event code in data.json	{{event_type}}	{{event_type:category}}
Obsidian starts	on-layout-ready	application-started	application
Obsidian quits	on-quit	application-quit	application
Switching the active pane	on-active-leaf-changed	active-leaf-switched	workspace
Caret moved in editor *	caret-moved	Same as in data.json	editor
Every n seconds	every-n-seconds	Same as in data.json	time
File menu **	file-menu	file-menu-item	menu
Folder menu **	folder-menu	folder-menu-item	menu
Editor menu **	editor-menu	editor-menu-item	menu
File content modified	file-content-modified	Same as in data.json	file
File created	file-created	Same as in data.json	file
File deleted	file-deleted	Same as in data.json	file
File moved	file-moved	Same as in data.json	file
File renamed	file-renamed	Same as in data.json	file
Folder created	folder-created	Same as in data.json	folder
Folder deleted	folder-deleted	Same as in data.json	folder
Folder moved	folder-moved	Same as in data.json	folder
Folder renamed	folder-renamed	Same as in data.json	folder

*) Caret moves in editor is still incomplete, and its details may change.
**) Menu events will have a trailing -item, because I'm thinking there might be file/folder/editor-menu-opens events in the future, that could allow executing shell commands already when a context menu opens up.

For events whose Event code in data.json differs from {{event_type}}, I'm planning to change the data.json codes sometime in the future, so that they will be the same as the {{event_type}} values.

[Taitava]

This was released earlier in 0.22.0.