I’d like to tell you where the Blue Griffon WSYWIG HTML Editor saves your custom configuration data and how you can transfer it to other Linux machines or save time configuring new releases. Very few NixMash readers may find this post useful, but out of curiosity I spent some time tracking this down so damn it, I’m going to blog about it.
I’ve tried all of the Linux Desktop HTML Editors and Blogging Clients and locked in on Blue Griffon, an application out of France. I’m using it to create this post, in fact. Here’s a screenshot.
Pretty nice, eh? One of things I really like about Blue Griffon is the ability to create keyboard shortcuts for darn-near everything you need to do.
Blue Griffon users enjoy an application which is actively being developed and receive frequent updates as a result. The downside of frequent updates is that you need to recreate your custom settings and preferences for the new release, at least in my experience. If you’re interested in where those Blue Griffon configuration files are located (all seventeen of you), here’s what’s happening.
Regardless of how you install Blue Griffon (I install to ~/.bluegriffon/version), Blue Griffon creates a hidden ~/.disruptive innovations sarl in your home folder.
Within this hidden folder, each Blue Griffon release (depending on the upgrade) creates its own configuration folder. The configuration folder path of my current release is
/home/daveburke/.disruptive innovations sarl/bluegriffon/knqqwmkk.default
This is where the action is. The file that is updated when you update keyboard shortcuts, for instance, is shortcuts.sqlite.
Shortcuts.sqlite is a Sqlite database. You can poke around in it with something like Sqlite Database Browser.
Another file you might be changing if you modify settings like word wrap would be prefs.js.
There may be a risk blithely dragging the configuration files of an existing version to a newer version and I haven’t used Blue Griffon long enough to advocate doing that. It only takes 5 to 10 minutes to configure each new version shortcuts for me, so I’ll probably keep recreating keyboard shortcuts and preference settings manually. Knowing how Blue Griffon stores configuration info may help those who deploy to multiple machines or who spend a lot more time customizing than I do.