Using plugins
Development reference · View source
| Key or command | Action |
|---|---|
:: | Open the plugin-only command palette, with completion and descriptions |
:plugins | Open the plugin manager |
:plugin-stop <id> | Stop a plugin, or cancel its pending restart |
:plugin-restart <id> | Reconnect after cleanup finishes |
Tab in an application view | Actions from its plugin |
Plugin commands:
- Plugins can declare short names, such as ru-time’s
::time,::time-add, and::time-delete. Full:plugin.<id>.<command>names always work. - Conflicting short names are disabled for all claimants and reported in
:notifications. Stopping a claimant restores a name once it is unique. - Backspace over the second colon returns to the ordinary palette.
- Keys for plugin commands are set with
plugins[].bindings.
The manager (:plugins) lists configured, disabled, and failed plugins.
Select one to see its capabilities, jobs, activity, helpers, and diagnostics;
Enter offers lifecycle actions.
- Restart does not replay old actions.
- Stopping keeps retained views readable and dirty provider documents editable.
- Persistent hosts keep plugin processes across detach and reattach.