Skip to content
BENIBIX Learn

/hooks Command

Also known as /hooks, Hooks menu

It lists your hooks and where each one comes from.

Think of it like

It is like a list of the house alarms, and who set each one.

Example

A hook keeps formatting Emma's files, and she cannot find where it is set. /hooks shows it comes from a plugin, not her settings.

Why it matters

Hooks run on their own, so a strange one is hard to trace. This shows each one and its source.

Definition

/hooks opens a list of the hooks set up in your session, which you can read but not change. Each hook says the event it runs on and where it came from: your user settings, the project's settings, a plugin or this session. Pick one to see the full command it runs and the file that holds it. To change or remove a hook, edit that file.

Example code

console
/hooks
See every hook and where it was set.
Each line names the event and the place the hook was set.

Common mistake

Trying to edit a hook in the list. The list is read-only. Change the settings file or plugin it names.

Key takeaways

  1. 1
    Read-only list. Every hook.
  2. 2
    Shows the source. Settings, plugin, session.
  3. 3
    Edit the file. To change one.

Learn it properly