Where Does clipmenu Store Clips and Cache?
clipmenu caches clips under CM_DIR (runtime/tmp fallback) with line index, locks and status files; launcher tweaks go in clipmenu.conf.
Last updated
clipmenu splits daemon from picker. clipmenud watches selections and writes hashed clip files plus a line_cache index into the cache dir resolved by clipctl (rooted at CM_DIR, defaulting through runtime and tmp dirs). clipmenu then pipes that index into dmenu or your launcher.
Persistence is opt-in via CM_DIR precisely because the default is ephemeral. Point it at ~/.cache or similar, keep CM_MAX_CLIPS sane, and the vacuum logic prunes orphans on trim.
Where clipmenu stores this, by platform
$CM_DIR (default $XDG_RUNTIME_DIR, else $TMPDIR, else /tmp)
Hashed clips, line_cache index, lock/status files. Resolve the live dir with clipctl cache-dir; CM_IGNORE_WINDOW skips password managers via xdotool.
Frequently asked questions
My clipboard history disappears after reboot. How do I keep it?
Export CM_DIR to a persistent path before starting clipmenud. Default cache lives under $XDG_RUNTIME_DIR (cleared on reboot) or /tmp, so clips vanish across logins unless redirected.
Custom launcher misbehaves with clipmenu. What is wrong?
Set launcher_pass_dmenu_args to 0 in clipmenu.conf. Custom launchers (fzf, rofi) otherwise inherit dmenu flags that break their parsing.
Notice an outdated path? Let us know.