Open LOQUILLO opened 10 years ago
ST 3 Build 3062 Windows 7 64bits
Gutter Color has changed my user settings.
Yikes that's a big ol' package crash. Might be some oddities with the Package Control vs git clone installation methods. (Though I think the Bower problems must be unrelated to us.)
Gutter Color has changed my user settings.
This should happen, but only if you used one of the "light color scheme fixes" as described in the readme. Did you run Fix Current Color Scheme
or set fix_color_scheme
in your user settings before this crash? And if so, did they work at the time? Does the color scheme file C:/Users/TEST/AppData/Roaming/Sublime Text 3/Packages/Gutter Color/MultiLanger-Dark2.gcfix.tmTheme
exist?
Hrm. Just realized that Package Control updates would probably erase themes kept in the same folder as the plugin itself. Dang. Should've thought of that!
I wonder if there's a .gitignore
equivalent for Package Control? Or maybe we should be using another folder anyway... Packages/Gutter Color Theme Fixes
or somesuch...
Well, if my above suspicions are correct, the temporary fix is simply to change your settings back to the unadjusted theme, and manually regenerate it.
The error should only happen on package control updates. So those who used the color fix between v0.2.0 and v0.2.1 are affected. I'll try to come up with a check that'll gracefully update everyone else.
Hi @tdhsmith I use customized settings for CSS(CSS.sublime-settings with his own scheme color CSS-Dark2.tmTheme), other for HTML(HTML.sublime-settings with his HTML-Dark.tmTheme), other for PHP(PHP.sublime-settings with his PHP-Dark.tmTheme), and for other language, etc, etc. Gutter Color break this customized config files changing "color_scheme": "Packages/User/MultiLanger-Dark2.tmTheme", for this line:Packages/Gutter Color/MultiLanger-Dark2.gcfix.tmTheme. I had fixed, and how, removing Gutter Color, and restoring customized settings, back install Gutter Color and voila, all is ok. Now is my fourth sesión openning ST3 and all is OK. Strange problem.
@LOQUILLO it'll be ok until one of your themes update.
@tdhsmith what if we store the customised theme inside the User directory?
@jbrooksuk sounds like a plan
I originally thought we could update people gracefully, by checking if their current color scheme file no longer exists. But what should we do when it's missing? It would be difficult to find the original because it could be zipped up in a .sublime-package
where python searching tools like glob
aren't going to find it. I don't know of any tricks to view the contents of package archives without a lot of overhead.
Should we just set the current theme to some sane default and display a little explanation?
Alternatively we could just leave accept the error as LOQUILLO experienced it, or else come up with a clever way to find the original theme.
This is the log:
And this is the image: