Closed evandrocoan closed 6 years ago
Hm, iirc this name is a relic from ST1 days and was replaced by the "Preferences" file we use today. If it still works for compatibility, we should probably add support for it. If it doesn't, we shouldn't and the Wrap Plus package should be updated to have that file renamed.
I am not sure if Sublime Text accepts Base File as Preferences, but the plugin itself works with Base File as settings name. Despite it, why just not load every file with the *.sublime-settings
as extension?
I checked its source code (as well as I could on mobile) and wasn't able to find a sublime.load_settings
call. It's all view.settings.
Then, it seems Sublime Text itself is ignoring the file called Base File.sublime-settings
I just verified that ST does indeed read files named Base File.sublime-settings
as it does Preferences.sublime-settings
, so the two can essentially be considered equivalent. Although the former is likely a backwards-compatible alias for the latter.
The package:
Name his settings file as
Base File.sublime-settings
. Then, it seems to causePackageDev
to not found the settings definitions for it: