The immediate question I ask is, "Why doesn't Label support a *Label style configuration?"

I don't expect any replies since this isn't an explicit bug or problem in need of resolve, but more a design issue.

What are the implications of breaking up those modules' step.rc commands which can perform an arbitrary number of actions?

For example, changing Label's Labels into the star-type command *Label, so that one may declare and define labels in separate files (that are optionally included).

But then you could argue that you could convert any command that executes something, such as RabidVWM's VWMOnSwitchTo.

Well, I only give few, specific examples which apply to a theme on a subjectively larger perspective. There aren't other cases I can think of that could use this in a practical way.

Is must be that this hasn't been done because this abstraction would introduce unneeded/unwanted complexity in both implementation and end-user configuration.

You can already specify multiple "Labels" lines.

Oh.
*blush*
*scrolls down changes.txt*
It's been there since version 1.3!? argh. (Still think it should should have been *Labels).
*embarrassment suicide*
*regains composure* erm.

Yes, it should have been "*Labels". Or even just *Label. And I think it never left changes.txt so label.txt still claims you can only specify it once.

It actually is in label.txt but it requires reading (oops) since it's right above the sample "Labels" line; having skipped most of the middle version releases, I never gave it the thought.

Nah, it's there:

To use multiple labels you need to have one or more "Labels" commands:

Oh sure, post something while my back is turned *and* don't let me nest tags ;)

Yes, it should have been *Label. If I ever rewrite the module, that's the way I'll do it.