Closed 0x64746b closed 12 years ago
This is intentional. The top-level status
key contains definitions of status applets. In contrast, the display:status
key contains instances of status applets. The YAML schema of both these things is similar because they are meant to override each other (instance body overrides definition body).
ok. That's weird. I considered that possibility but 'confirmed' twice that a top level status
section would fail (with sth like status is not a mapping
or sth?). Sry for spamming your bts ;/
The status is not a mapping
error comes from the YAML schema validator, so that's good: at least we know your YAML input is being validated correctly.
README.markdown
containsstatus
as a top level config option in addition to astatus
subsection underdisplay
.