atom/atom — pull request #3944 by benogle (2014-10-24 00:24:56+00:00)
Title: Give scoped user settings a priority

Currently, the user's config file is loaded, then when each package loads, their config settings are loaded on top. Packages that define scoped settings will have priority over the user settings because they are loaded last. Example: atom/settings-view#267 We have a few options:

* Load the user config _after_ all the packages.
* This produces a period of time when atom has no styles.
* Requires adding a pretty awkward method on PackageManager to get a callback when the scoped settings are all loaded
* Load the config as it is today, then reload the user config
* Requires adding a pretty awkward method on PackageManager to get a callback when the scoped settings are all loaded
* Loads the file 2x
* Keep track of the read config file, and reload the scoped properties when the packages load
* Requires that awkward method
* Seems like it would add some complexity to config
* Give the user configs an explicit higher priority
* This PR

This feels like the cleanest, least intrusive way to do it.

Closes atom/settings-view#267
Depends on https://github.com/atom/scoped-property-store/pull/6