Where Is the Hikari Config File?
Hikari Wayland compositor config file, autostart script and fallback paths.
Last updated
Hikari reads a libucl config from XDG with a system fallback. A config flag redirects to any path. Packages often ship a sample beside the fallback.
Startup programs go in a separate executable file. An autostart flag overrides that path too. Default terminal resolution leans on the environment, not the config.
Where Hikari stores this, by platform
~/.config/hikari/hikari.conf
Libucl format config with system fallback and sample. Autostart script runs once at startup. Both paths overridable via launch flags. Linux and FreeBSD only.
Frequently asked questions
How do I back up Hikari?
Copy hikari.conf plus the autostart script with the compositor stopped. Restoring means putting both back and launching once to confirm bindings and outputs. Keep the launch flag path in mind on odd setups.
How does the autostart script work?
Mark the file executable and keep it at the default path, or pass a custom one with the autostart flag. It runs once at startup for daemons and helpers. The default terminal comes from the TERMINAL variable.
Notice an outdated path? Let us know.