I don't really understand this. Before we had a test which tested the aspects already supported. For every added supported rule the test was added. Obviously this was not complete, it's not news that rules are fully implemented yet.

Now we have more test cases also for the things not yet supported, but the complete test is skipped. Thus also the already working aspects are not covered. I don't understand what the advantage is.

Can we expose the enums as public and use them here.

Yeah, it's a very good idea. Whould it be enough to expose only

// All these values are saved to the cfg file, and are also used in kstart!
enum {
    Unused = 0,
    DontAffect, // use the default value
    Force,      // force the given value
    Apply,      // apply only after initial mapping
    Remember,   // like apply, and remember the value when the window is withdrawn
    ApplyNow,   // apply immediatelly, then forget the setting
    ForceTemporarily // apply and force until the window is withdrawn
};

?

And StringMatch