I have what is effectively an erb file, but it is not highlighting embedded css or tags correctly. No coloring on any tag attributes and no coloring at all for css. Tag names show up as yellow, but thats it. I am using the Dobdark tmtheme. I also added rules to highlight annotations in javascript , but those no longer highlight. I changed my theme to give the full scope path and it still didn't highlight them. I have a screenshot if you need one.

Could you also provide some insight into how scopes are actually ranked against various scope selectors. Is it done more or less like css?

Also, would it be possible to have a version of ctrl+alt+shift+p that does not disappear after 5 seconds? It's so annoying when I am trying to type the scope and it disappears . Also, would it be possible to have a keybind to print the color of the current text, or at least the theme rule that it is using? The reason is sometimes I like to copy a color from one section of my theme to another, but I'm not sure which color it is. Without a theme editor it is really hard to figure it out?

While the find panel is open, I can still edit my document, except for the "enter" key. Now the enter key is always passed to the "Find" button... previously I thought this happens only when the blinking cursor is active in the find panel.

Also, when I hit "Find all", the find panel disappears. I thought I used to hit "Find all" and then "Replace all" without re-activating the find panel.

[edit: this is actually dev 2098, i haven't used 2099 yet]

Last edited by oats on Mon Aug 08, 2011 6:08 pm, edited 1 time in total.

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: