Few issues/improvement ideas (i'm on windows, i have no idea what's happening on other platforms):1) Maybe it's a good idea to set the background of the scope settings tab to be the same as the theme background, otherwise....2) double click on a scope to edit. Press Esc. Nothing happen (it should either go away silently, something like a Cancel)

1.) Are you sure it isn't? For me, the editor sets the rows of all entries to their defined background color, and if not, it sets the background to the global background. If you aren't defining a global background, then I think it will default to white, just like Sublime does. Is this not what you are seeing?

2.) Yeah, I like that, it was on my list...the list in my head which I should have written down so I wouldn't have forgotten this .

The editor is Sublime agnostic, but yes, the plugin half has only been coded for ST3. If anyone wants to create a ST2 branch and get it working on the repo, that would benefit a number of people, but it is enough work right now getting the editor finished and working on all platforms; I have no intention right now to backport the plugin half to ST2. I am using ST3 as my main editor, so all of my work is mainly going to be directed there.

-Ensure when font styles are removed that cells get their style updated-Settings dialogs are now "dialog" type to ensure parent is disabled.-Esc key now closes settings dialogs-Add button panel for move, add, delete rows-Threaded "Live Save" manager to manage when live saves occur in order to keep from getting XML errors in sublime

Let me know if XML errors are still occurring. As far as I know, that is all of the bugs; I am currently done with adding new features for now I think. I am now going to try and get Linux going.

Oh man, you are awesome, thanks for the update! Unfortunately, Esc doesn't close the edit popup.

Anyhow, here are few more ideas:- click on [+], the popup show up and, in background, a new row it's added. If i cancel the editor, the new row is still there. Actually i think it should go away if you cancel.- i've noticed that some themes have some much more scopes compared to others (space cadet i think it's the less equiped to say so; sunburst, on the other hand, has a lot of options). Although i believe that scopes are defined on tmLanguage files, not on theme, ii guess it would be nice to have a list of commonly used scopes. Something like a combination between text field and selectbox.- a dropdown for selecting other themes

Btw, i think i asked couple of times in the past (but i'm old and i forget shits) there is a way to extend a theme? I mean i like dark themes, but not all (if any!) has brackethighlights or linter scopes. So it would be nice if there was something to say: use this common styles for all themes.

1. Esc works on Mac at least, I will confirm on windows, if not I will tweak the code again.

2. Current [+] implementation is to add row and then edit it (it was quickest and easiest this way). But I understand why this might not be desirable, and your suggestion is a good one. Only because it isn't critical, I won't be jumping on it right away; I will look into better workflow when I get a chance. I was more concerned about getting it functional fast at this point.

3. I can understand the desire of having a list of commonly used scopes...who's going to compile this list ? I am building the editor, if someone wants to do some legwork to compile a list of common scopes, I may add a way to import the list; probably as an external settings file.

4. What do you mean a dropdown for selecting other themes? What other themes? The editor simply gets pointed at the theme files via a file picker or command line. It isn't tied to sublime in anyway, so it doesn't know where to find themes without help. Do you mean the plugin side should scan sublime for theme files? Please elaborate.