michaelworm/SoDaReloaded-Theme

Latest update broke the theme

m1keil opened this issue · 8 comments

Hey,
My sublime just went crazy after the last theme update. Totally broken.

preferences sublime-settings cloudify-nodecellar-example-master 2015-09-29 18-05-37

Tried reinstalling the theme, got same results. Soda theme works.

Hey,

did you try to restart Sublime Text? And if this did not work, try to reinstall the theme (remove and install again).

Because I added a light variant all paths are different now.

Hope this helps, if not I will have a look tomorrow.
Sorry for the inconvenience.

Am 29.09.2015 um 17:05 schrieb Michael Sverdlik notifications@github.com:

Hey,
My sublime just went crazy after the last theme update. Totally broken.


Reply to this email directly or view it on GitHub.

Hey,
thanks for the response.

Yep tried the usual restart sublime, re-install theme and even tried the light version instead.
I wonder if there's some error log I can check...

Sorry, tried the whole remove/install cycle again just in case and now it seems like it did the trick.
Thanks!

No problem, good to hear that it worked out well ;)

I am experiencing the same issue on Windows 10 Pro. Unfortunately, removing and re-installing the theme did not work for me. Restoring a backup of my settings directory from last week fixes it, but as soon as the theme is updated, everything breaks again the next the I open Sublime Text.

sublime text 3

I figured it out. In v1.0.0 the theme name changed from SoDaReloaded to SoDaReloaded Dark, as @Miw0 comments above. There is no need to reinstall the theme. To fix, follow the steps below:

  1. Go to Preferences -> Settings – User

  2. Locate the following line:

    "theme": "SoDaReloaded.sublime-theme"
  3. Change it as follows:

    Dark variant

    "theme": "SoDaReloaded Dark.sublime-theme"

    Light variant

    "theme": "SoDaReloaded Light.sublime-theme"
  4. Save

Changes take effect immediately; I did not even need to restart Sublime Text.

oohhh.... yea that might explain it.

Oh yea well you're right, my fault.
Good to hear that it works now and many thanks to @dliuzzi to point that out :)