~/vimma/docs $ less theming.md

Theming

Vimma's own parts of the window, the status bar, the command line, the pickers, link hints, pane borders and the start page, share one colour theme. Out of the box it is Tokyo Night. (This site wears the colours of Vimma's logo instead; the browser's theme is yours to pick.)

Where the colours come from

Your own colours

Set colours under [theme.colors] in config.toml. Save, and every window recolours within two seconds:

[theme]
source = "file"     # the built-in Tokyo Night; leave this out to follow Omarchy
[theme.colors]
accent = "#ff9e64"

To use Tokyo Night on Omarchy without a config file, set vimma.theme.source to builtin in about:config.

With Omarchy

There is nothing to set up. Switch themes with omarchy-theme-set or the Omarchy menu, and every Vimma window follows, without a restart.

So that it changes at the same moment as the rest of your desktop, Vimma puts a small hook, vimma-theme-reload.sh, in ~/.config/omarchy/hooks/theme-set.d/ the first time it starts. Edit it and Vimma leaves it alone; delete it and it does not come back. Without the hook, Vimma still notices a new theme within two seconds.

Details

Everything below is Vimma's own user guide for this topic, in full: every edge case and exception. You do not need it to get started.

Colours: your Omarchy theme

The status bar, the command line, the ctrl+b ? overlay, the pickers and prompts, link hints, notices, pane borders and the start page take their colours from your current Omarchy theme, with nothing to set up: Vimma reads ~/.local/state/omarchy/current/theme/colors.toml (and light.mode, for a light theme) and checks it every 2 seconds, so omarchy-theme-set (or picking a theme from the Omarchy menu) recolours every open window and start page within 2 seconds, without a restart. Without Omarchy, or with vimma.theme.source set to builtin, the colours are Vimma's built-in Tokyo Night. A colors.toml Vimma cannot read (a value that is not a #rrggbb colour, a missing key) is ignored: the colours stay as they were, and the Browser Console (ctrl+shift+j) says which line is wrong.

Instant theme changes. On Omarchy, Vimma recolours as soon as omarchy-theme-set finishes, not within 2 seconds, with nothing to set up. When Vimma starts and finds ~/.config/omarchy/hooks/, it writes its hook, vimma-theme-reload.sh, into ~/.config/omarchy/hooks/theme-set.d/ (mode 0644). Omarchy runs that hook after every theme change; it tells each running Vimma to read the theme again, through the same channel a second vimma command uses to reach the running one (no control socket, no vimma-ctl). With Vimma not running, the hook does nothing and starts nothing. Omarchy runs its hooks after it has restarted the terminals and retinted the other apps, so Vimma changes together with them.

• Your edits stay yours. The hook's last line is a checksum. As long as it matches, Vimma keeps the file up to date; once you edit the file, Vimma never writes or removes it again.
• Deleting it sticks. Vimma writes the hook once; if you delete it, it does not come back.
• To opt out, set vimma.theme.omarchyHook to false in about:config: Vimma removes its own, unedited hook at once and writes no new one. Set it back to true to have it written again.
• By hand: vimma -vimma-reload-theme makes the running Vimma read its theme now. Only use it while Vimma runs: with none running it starts Vimma (the hook checks first, so it never does).
• Without D-Bus, the hook falls back to vimma-ctl reload-theme when vimma-ctl is on your PATH and the control socket is on.

The 2-second check keeps working in every case.

Known limits

Vimma is pre-alpha. What does not work yet, or works with a catch, is listed on the known limits page:

• Features

The guide at the top is written for this site; the details are built from Vimma's docs/guide.md and bindings.md at 1050bcc (2026-10-10).