Where Does Trippy Store Config?
Trippy reads tracing options from trippy.toml found via flag, cwd, home, or config dirs, with CLI flags winning.
Last updated
Trippy looks for trippy.toml (or dot-prefixed) in several spots: explicit flag first, then current directory, home, XDG config roots, and %APPDATA% on Windows. CLI flags override file values item by item.
That precedence decides debugging. When output surprises, check for a stray trippy.toml in cwd shadowing the intended one. Generate the template to see every tunable rather than guessing key names.
Where Trippy stores this, by platform
~/.config/trippy/trippy.toml
trippy.toml lookup: flag, cwd, home, XDG roots. Generate a template rather than hand-writing; flags override file values.
~/.config/trippy/trippy.toml
Same lookup chain as Linux. Homebrew installs share these paths with cargo installs.
%APPDATA%\trippy.toml
Same chain ending at the Windows data directory. Explicit config-file flag beats every implicit location.
Frequently asked questions
How do I create a Trippy config file?
Run trip with the print-config-template flag and redirect to trippy.toml in ~/.config/trippy. Edit themes and bindings there instead of long flags.
Trippy ignores my config file. Why?
Pass the explicit config-file flag pointing at it. Trippy's search order may otherwise pick a different trippy.toml earlier in the chain.
Notice an outdated path? Let us know.