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]