Settings parent child hierarchy

This implements settings hierarchy for editor and view as discussed [here](https://github.com/limetext/lime/issues/197). closes #197
Can we consistently use one scheme for our default files? My vote is for tabs, just because that's what we use for the go code.