Where Does Walker Store Config?
Walker reads config.toml plus themes from the walker config folder. Elephant providers run as a separate service.
Last updated
Walker splits config from data providers. The walker folder under XDG config home holds config.toml with placeholders, prefixes, keybinds, and theme choice, plus a themes subfolder with CSS and layout XML. Elephant runs separately as the provider backend.
Nix users get the same files generated from home manager options. The default config in the repo resources is the reference template. Service mode plus socket calls keep launches instant. Provider enablement lives in elephant config, not the walker folder.
Where Walker stores this, by platform
/home/<username>/.config/walker/config.toml
Main config in TOML. Placeholders, prefixes, keybinds, and theme name. Compare with the repo default on upgrades.
/home/<username>/.config/walker/themes
CSS plus layout XML per theme. Inherits the default theme, so overrides stay small.
Frequently asked questions
How do I migrate Walker settings?
Copy the walker config folder to home config on the new machine. Themes and provider prefixes travel together.
Walker shows nothing. What runs first?
Ensure elephant runs first with providers installed, then launch walker as a service for speed. The socket call opens it instantly.
Notice an outdated path? Let us know.