-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does not work on with ST3 build 3059? #97
Comments
Can you provide a screenshot? Sounds like there's a syntax error in the .sublime-theme file. If there are any errors in the console, post them as well. |
@markcol have you still having this issue? If not could you please close this issue? |
I'm having the same issue— build 3059. |
Also having this issue with build 3059. |
1 similar comment
Also having this issue with build 3059. |
Same here with issues on 3059. Found the theme was listed in my "ignored_packages" in user prefs. Removing it from there solved the issue. |
+1 |
I've seen that issue off and on for the past couple of months on ST3. Could never track it down though. Had to uninstall and reinstall Flatland once to get it fixed. The last few times it has seemed to resolve itself though. I'll try to grab the console log the next time it happens. |
@pablofierro Looks like a syntax error in the .sublime-theme file. I see it a lot when I'm making theme edits and forget a comma or closing bracket. That weird pattern seems to be the default image for everything. If that's the case the console will tell you that there was an error processing the theme file. To confirm this you could try removing all comments and then running it through JSON Lint to see if there are any obvious errors. |
Tried that with |
Ran into this issue when upgrading from Sublime Text 3064 (dev) to 3065. As @dylansmith pointed out, Flatland Dark was added to ignored packages. (I've ran into this in the past as well, but I always forget to check ignored packages) |
I installed the package and there were a number of rendering issues:
There may have been others, as well, bit it was clearly not working as expected, and was not usable.
To ensure that it was not a conflict with other packages, I reproduced the behavior by:
The results were the same.
The text was updated successfully, but these errors were encountered: