Increase flexibility of compound options. about wf-config

[ammen99]

Moving this to wf-config as currently it is the place where the config file parsing is implemented.

Generally, I (and many others seem to) agree with you that this is cumbersome. However, I have two objections:

1. The syntax you mentioned seems very close to the 'object' syntax. objects are for example outputs, where you define a config section of the type [output:<something>] and then you have the same options for each object. While objects have their perfectly valid uses, I think that (ab)using objects to represent lists like compound options is a bad design, as it mixes options and sections.

2. I am also unsure whether piling more things on top of our INI syntax is a good idea. Maybe someone should develop an alternative Wayfire config backend with YAML/JSON/whatever format, port WCM to it (I think many of the Wayfire users find WCM a very useful piece of software) and then merge it upstream as a better alternative.

The ini file format seemed a good fit in the early days of Wayfire, as indeed all configuration options were simple values to be fed to the plugins. Nowadays, with objects and compound options it looks more and more like a little bit more complex config format would be preferable.