Quassel Config File Format » History » Version 1
TC01, 08/07/2017 03:09 AM
| 1 | 1 | TC01 | h1. Quassel Config File Format |
|---|---|---|---|
| 2 | 1 | TC01 | |
| 3 | 1 | TC01 | The monolithic quassel client, the distributed quassel client, and the quassel core binary all write a config file. For the core, this configuration file primarily contains connection information for the configured database backend. The client(s) have much larger configuration files, containing among other things local UI settings. |
| 4 | 1 | TC01 | |
| 5 | 1 | TC01 | The config files encode QVariants into strings in a number of places rather than simply storing raw, human-readable data. This makes it easy for quassel to load and save the configuration but difficult for a human to figure out what's going on, or modify it. |
| 6 | 1 | TC01 | |
| 7 | 1 | TC01 | For more information on QVariants, please see the Qt documentation: https://doc.qt.io/qt-5/qvariant.html |
| 8 | 1 | TC01 | |
| 9 | 1 | TC01 | h2. quasselconf |
| 10 | 1 | TC01 | |
| 11 | 1 | TC01 | quasselconf is a small program that parses a quassel configuration file and prints a human-readable version of it, decoding all QVariants. It is a community tool written by TC01 (#quassel on chat.freenode.net). It's available on gitlab here: https://gitlab.com/TC01/quasselconf. if you have bugs or feature requests, please ask on IRC or file them here. |
| 12 | 1 | TC01 | |
| 13 | 1 | TC01 | The main usage case for this is to check the database connection information that's been saved in a core config file. |