Skip to content
NeruNeru nightly
Nightly docs track main and may describe features that are not released yet. Docs for the current release (v1.57.0) are here.

Scripting

Every hotkey step is also a shell command, so anything a binding does, a script, a launcher or another hotkey daemon can do too. Each neru command prints its reply, writes errors to stderr, and exits non-zero on failure. Commands are in the CLI reference, and the neru status --json fields under neru status.

Pause and resume Neru

Section titled “Pause and resume Neru”
Terminal window
if [ "$(neru status --json | jq -r .enabled)" = true ]; then neru stop; else neru start; fi

Check whether the daemon is running

Section titled “Check whether the daemon is running”
Terminal window
neru status &>/dev/null && echo "Running" || echo "Not running"

Drive Neru from another hotkey daemon

Section titled “Drive Neru from another hotkey daemon”
~/.config/skhd/skhdrc
ctrl - f : neru hints
ctrl - g : neru grid
ctrl - r : neru hints --action right_click

Run several steps as one unit

Section titled “Run several steps as one unit”

Use neru run instead of chaining neru calls with &&. It sends the whole sequence in one request, under hotkey binding rules.

To leave every global hotkey to the other daemon, see Recipes.

Talking to the daemon directly

Section titled “Talking to the daemon directly”

To skip the neru binary, send JSON over the socket. The format is in IPC protocol.