Where Does Tridactyl Store Keymaps and RC Files?
Tridactyl keeps keymaps in extension storage with an rc file for versioning and a native messenger for system access.
Last updated
Tridactyl stores settings in extension storage inside the active profile. Keymaps, search aliases, and theme choices live there, sourceable from an rc file you keep. The native messenger adds system-level features beside it.
That trio defines migration. Extension data moves with profile tools or sync. The rc file versions in dotfiles for everything mappable. Native messenger installs per machine through its own command.
Where Tridactyl stores this, by platform
%AppData%\Mozilla\Firefox\Profiles\<profile>\storage (per profile)
Settings per profile plus versionable rc file. Native messenger installs per machine for system features. Source the rc after fresh installs.
~/Library/Application Support/Firefox/Profiles/<profile>/storage (per profile)
Same model on Mac. Native component enables external editors. Rc file keeps mappings identical everywhere.
~/.mozilla/firefox/<profile>/storage (per profile)
Profiles under ~/.mozilla with the same workflow. Dotfile the rc and reinstall the messenger per host.
Frequently asked questions
How do I move Tridactyl to a new browser?
Save your rc file with settings plus extension data, then source it on the new profile after installing the native messenger. The rc carries mappings; the messenger enables system features.
Does Tridactyl need its native messenger?
Yes for full power. Edithint and external editors need the native component installed per browser. Pure browsing keys work without it.
Notice an outdated path? Let us know.