Another theme-related bug-- I use one (Tomorrow-Night) which works great. For Widget.sublime-settings, I set the syntax to a .tmLanguage file based on Python, which colors the console's output. Now (after this release), it doesn't. But if I switch themes, it works again. Weird.

jps wrote:Along with the new selector implementation, there are several new API functions to expose the selector scoring function (allowing multiple selectors to be ranked vs a scope), adding the ability to select with arbitrary selectors and scope names (rather than having to source a scope name from a point in a view), and being able to search the buffer for regions matching a given selector (e.g., view.find_by_selector("comment") will give you all the commented out regions).

ajpalkovic: thanks for the useful bug report - the issue is fixed now in 2100. Color scheme rules were being applied in the opposite order they should have been, so the least specific rule was taking precedence.

The selector scoring rule is essentially rightmost longest: the rightmost space separated portion, and then matching the longest portion of this. e.g., for the scope "source.c++ comment.c", selectors would rank in this order:

Can you explain why not? I find screencasts help show exactly what is going on. Ever heard the expression, a picture is worth a thousand words? Well I find a "videos videos" is worth a million. Count me out of reporting any more bugs or submitting patches to plugins if that's the response I get back.