Where Does Darcs Store Config?
Darcs layers config from the global ~/.darcs folder down through _darcs/prefs in each repo, with a shared patch cache beside it.
Last updated
Darcs configuration is a small stack with clear precedence. The ~/.darcs folder holds your global defaults: author identity, boring-file patterns, and default flags. Each repository adds _darcs/prefs with project-specific overrides that win over globals. The boring file deserves early attention: patterns you never want patched (build outputs, editor backups) belong there from day one.
The same home folder also hosts the global patch cache. That cache is why a second clone of a big repo feels instant: patches come from disk instead of the network. Treat the prefs as precious and the cache as disposable.
Where Darcs stores this, by platform
~/.darcs
Global defaults, boring patterns, author identity, and the patch cache. Repo files in _darcs/prefs override anything here. darcs setpref writes the repo tier, never this one.
~/.darcs
Same global role as on Linux. Per-repo prefs live in _darcs/prefs inside each checkout. Temp dirs default to /tmp with _darcs as fallback, overridable per repo.
%APPDATA%\darcs
The Windows equivalent of ~/.darcs, holding the same defaults and cache. Per-repo prefs still live in _darcs\prefs with backslash paths, same precedence rules.
Frequently asked questions
A setting I set globally has no effect in one repo. Why?
Check _darcs/prefs/defaults in the repo first, then ~/.darcs/defaults. Repo prefs beat global ones, so a project file explains most surprises. The darcs help for setpref lists every settable preference.
Can I delete the Darcs cache to free space?
Yes. The global cache avoids re-downloading patches across clones and enables hardlink sharing. It regrows on demand, so wiping it only costs bandwidth and time, never data.
Notice an outdated path? Let us know.