Where Does Kupfer Store Config and Plugins?
Kupfer keeps config in .config kupfer on Linux with plugins in local share. Favorites and triggers use pickled state files.
Last updated
Kupfer splits config from code cleanly. Settings, favorites, triggers and mnemonics live under .config kupfer while custom plugins branch under local share. Manpages document both trees.
Mailing-list threads confirm the layout against autostart entries beside it. Plugin formats span files, packages and zips with environment gates. Copy config plus plugins for full migration.
Where Kupfer stores this, by platform
~/.config/kupfer/kupfer.cfg
Main config with favorites, triggers and mnemonics pickles beside it. Autostart entries live one level up. Copy whole while quit for migration.
~/.local/share/kupfer/plugins
Custom plugins as files, packages or zips under local share. Audit sources before installing. Environment flags gate loading for troubleshooting.
Frequently asked questions
How do I back up Kupfer?
Copy ~/.config/kupfer whole with Kupfer quit, including kupfer.cfg with favorites and triggers pickles plus mnemonics. Custom plugins live separately under local share. Autostart entries ride along untouched.
How do I install Kupfer plugins?
Install single files or packages into ~/.local/share/kupfer/plugins with zip support. Treat plugins as code and audit sources. Disable loading through environment flags when troubleshooting.
Notice an outdated path? Let us know.