Each settings file should be in its own separate settings object. Otherwise consider what happens when we want to re-load one changed settings file without breaking the settings "priority" ordering; we'd need to reload all children in the priority ordering too as we don't know which setting comes from which file.

This is why the Settings object has the [Parent](http://godoc.org/github.com/quarnster/util/text#Settings.Parent) and [SetParent](http://godoc.org/github.com/quarnster/util/text#Settings.SetParent) functions, as this lets us manage the priority of the objects and just reload a single file if that file changes. Does that make sense?

Same should go for keybindings, menus et al but IIRC there's no code written for managing this kind of Parent/Child priority for those items.