Closed AllanLRH closed 7 years ago
I think it trying to load a scheme which you don't have on disk.
Check which scheme is set and try to load it. Open any view and the console
scheme = view.settings().get("color_scheme")
sublime.load_resource(scheme)
It smells like a conflict with another package. Did you install some new packages lately? Great issue report.
I just got a new macbook, so I got an entirely new system, where I kept my old User-folder, which caused all the previously installed packages to be automatically installed by Package Control (once Package Control was installed). That's of course a bad foundation for providing a bug-report, which is why I reverted to a freshly installed state before submitting the bug report — the issue persisted in the "fresh state". But downgrading the the previous DEV-build (3153 instead of 3154) seems to have solved the issue.
Indeed, when I ran the commands like you asked me to I got this running 3154:
>>> scheme = view.settings().get("color_scheme")
>>> sublime.load_resource(scheme)
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/Applications/Sublime Text.app/Contents/MacOS/sublime.py", line 192, in load_resource
raise IOError("resource not found")
OSError: resource not found
>>> scheme
'Monokai.sublime-color-scheme'
I tried reinstalling ST 3154, but it didn't help.
Downgrading to 3153 made print(sublime.load_resource(scheme))
print the content of the XML-file which contains the Monokai color-scheme.
If this is really a bug in ST 3154, should I change the title of the issue and keep it open, or should I close it as resolved, since the issue can be circumvented... it could be a bug in the DEV-version of ST?
P. S.: Thanks for the help :)
EDIT: I've asked whether other people have encountered similar problems in the Build 3154 thread on the Sublime Text Forums.
Closing since it seems to work in ST Build 3155.
But the response from the ST forum might be of interest to the maintainers (@stoivo ?):
Pretty sure it's not a bug - color schemes IIRC used to have to be referenced by their full path (.tmTheme files), but now with .sublime-color-scheme files, it doesn't make sense to do so, nor is there generally any need for a plugin to try to directly open a .sublime-color-scheme. If it is absolutely necessary, GitSavvy should probably use sublime.find_resources first to get a full path to the file
I reckon that a workaround would be adding Packages/Color Scheme - Default
before the name of your default color scheme.
"color_scheme": "Packages/Color Scheme - Default/Mariana.sublime-color-scheme",
@AllanLRH
indeed, it is an issue of GitSavvy #829 and a fix #830 has been proposed.
Same problem can occur if an old style color scheme is set in the user preferences. Removing that line solves problem.
Can't get inline diff viewing to work (git: status, l), although normal diff does (git: status, e).
Steps to reproduce
~/Library/Application Support/Sublime Text 3
)Software versions
Logs and settings
Console output
Since the console log suggests that there's a missing resource, I checked the function which raises the exception in the file
/Applications/Sublime Text.app/Contents/MacOS/sublime.py
:Gitsavvy log
GitSavvy settings
git-settings
Contents of
~/.gitconfig
EDITS: