The current way package specific settings are stored is likely to raise problems in the future. I already discussed this with another user in the IRC channel and we didn’t seem to agree; I’ll simply paste the log of the conversation here because I think it does a decent job at explaining the problems I foresee. Parts between enclosed brackets are edited for clarity:
[quote]…]
Hey there, quick question regarding the Sublime Text 2\Packages\User\Base File.sublime-settings file
This configuration file is apparently used by several different packages that I’ve got currently installed, e.g. SublimeLinter and and SublimeCodeIntel
Is this a fault of Sublime Text 2 or how the individual packages handle user-specific settings?
Base File.sublime-settings is the old name, it’s called Preferences.sublime-settings now
it contains all the user specified settings, and some plugins define their own
I’m not sure what you mean by ‘fault’
Well… I do have a Preferences.sublime-settings file
But when I navigate over Preferences->Package Settings->SublimeLinter->Settings - User
Sublime Text opens the Base File.sublime-settings
in the earlier mentioned directory
the plugin hasn’t been updated to account for the name change then
So in case they do get updated: I have mixed key-value pairs for different plugins in a single file?
you can place your settings in Preferences.sublime-settings, and they will almost certainly still be picked up by the plugin
yes
Isn’t that a bit short-sighted? As in what happens if 2 packages have the same key
no, it’s not
you could say the same thing about what if two plugins pick the same config file name
or the same plugin name
That’s why having package-specific user settings file is a good idea
or at least a convention to name them accordingly “Package Name.sublime-settings”
This currently certainly isn’t a good solution
no, that would be painful
That would be well planned
currently there’s one place to put all configuration settings
splitting them up between multiple files would just add complexity for no return
Except that it wouldn’t really. Sublime Text 2\Packages\User<Package Name>.sublime-settings or alternatively Sublime Text 2\Packages\User<Package Name>*.sublime-settings
There’s not much more complexity there and it prevents that fault
Also there’s not really a difference for the end user if you access these files over the menu shortcuts
there’s a large difference, as now the user would have an explosion of menu items
and it doesn’t solve any problems
The amount of menu items stays the same
And it does solve the earlier mentioned problems
Maybe we are talking about different things, let me take a screenshot
*
So one would access Preferences/Package Settings//(Settings – User|Settings – Default)
If you click “Settings – User” Sublime Text 2 opens] Sublime Text 2\Packages\User<Package Name>.sublime-settings or alternatively Sublime Text 2\Packages\User<Package Name>*.sublime-settings
And as mentioned the amount of menu items would stay the same, so I don’t see what you mean
jskinner, ping
…]
As a tradeoff Sublime Text 2 could still prioritize the settings found in Preferences.sublime-settings, so you can keep all your settings in a single file until the scenario I mentioned earlier occurs
…]
*[/quote]