Sublime Forum

Theme disabled after update, needs restart to re-enable

#1

For reference: I’m running ST3 x86 build 3065 on Win8 Pro x64 and Win8.1 Pro x64 (and until recently, Win7 Ultimate x64) along with the Seti_UI theme, using Themr to apply my themes. If you need any further details of my environment, just ask.

At the startup update check, ST3 flashes a message at the bottom about reverting to the default theme and my sidebar/tabs get reset. After the update is complete, I always see the following behaviour:

  • I open the command palette and try reselect the Seti theme, but it’s not in the list. At this point I need to restart ST3 in order to select my theme from Themr again.

  • After a restart, I select Seti through Themr and it half applies; the tabs, text colour and sidebar icons change, but the sidebar background colour does not.

  • After one final restart, everything looks correct again.

Note: If I set the theme manually after the update, I can avoid the issue of Themr not refreshing it’s list, but the sidebar styling still only comes right after a restart.

I know Seti itself has had quite a few updates recently, however I’ve seen this behaviour many times recently, I suspect with other updates as well. I can’t see anything useful in the console output when all this happens though… I can’t tell if this is a problem with how Package Control handles package updates, how Sublime handles reloading stuff, how Themr refreshes themes, or with some combination of the lot.

Is anybody else having issues like this? I tried searching the forum, but nothing similar came up in my search results. This is getting highly annoying and I can’t figure out how to get around this start-restart-restart process after what feels like virtually every package update.

0 Likes

#2

Possible that it’s Package Control viewtopic.php?f=3&t=13750&start=0&hilit=sublime+glitch#p60372

0 Likes

#3

Interesting, thanks for the info subhaze. :smile:

This same issue actually just came up again a few minutes back… Looking at the console output with this new found knowledge, it seems the “ignored_packages” entry is actually altered during the update process.

Something interesting: I just tried removing the “ignored_packages” entry from my user settings file, but after restarting ST3 it seems to be back again. While now it only lists the “Vintage” and “JavaScript” packages, previously this list included “NSIS”, “Vintage”, “LESS”, “Markdown” and “JavaScript”.

Either way, I’ll run like this for a while and see how it goes.

0 Likes

#4

That’s correct, Package Control has to do this during the install/upgrade process of packages so that ST doesn’t freakout with all the file changes happening underneath it.

Usually after any large amount of package updates I’ll double check my ignored packages list just incase something got left in there.

0 Likes

#5

It seems clearing the “ignored_packages” entry has made some difference to the issue I was having, after an update all themes are listed correctly again in Themr. It still confuses me that certain packages get added to this array (correctly so, as per the update/reload procedure I’ve observed) but then don’t get removed again. It’s very rare, but this is the only point that’s actually breaking anything on my side. I don’t have enough info to warrant a bug report though, so I’ll have to just keep an eye on it and hope for the best.

As for the sidebar with loading a new theme, I’m guessing that’s more a Themr issue than a Sublime issue… As annoying as it is, it doesn’t break anything.

[edit]

Didn’t actually notice your message before I posted my reply… I’ve inadvertently started doing the same thing anyway, to the point that I wish I could assign a keyboard shortcut to it. :smile:

0 Likes