Yes, it will be automatic...which is what I am a little worried about.

I imagine I am going to get a bunch of bug issues of "why is X not working like it used to", "what happend to my shortcuts", "where did my colors go", "Why are my setting in BracketHighlighter.sublime-settings not working". I am going to have probably a good couple weeks of a lot of people freaking out without reading the documentation. I wish I could get the messages.json working properly with my package in Package Control, but I never have figured it out.

So really if you are waiting for the official version, just sit tight and you will automatically get it. I wanted to get it nice and stable and ensure that my new design was not going to have negative effects before I pushed it out on people...but if your curious, it is working real nice .

I realize the new settings file(s) are a bit more complicated, but this allows custom brackets which people seemed so badly to want. The more flexibility that is desired, the more complicated the system. It saves me a great deal of trouble though, because now custom brackets can be added without me ever touching the core code...I can't tell you how happy I am about that .

The messages.json is a bit odd. I've noticed (at least before the update, but I assume it's still the same), that the commit/version times are based on EST. I normally add a couple hours to the current time, then offset it to EST. It may be worth giving it a shot, since, as you said, may users will ask you why x,y, and z are not working anymore. In the worst case scenario, no one gets your message and you get all the issue creation you expect. In the best case, it works and people will (hopefully) read about the updates on the README. Setting up the messages themselves is pretty straight forward. I'm sure you have looked through the same documentation I have on wbond's site.

Anyways, that's my insight into the messages system of package control. I think it's worth giving it a shot since, even though I'm sure you will answer the "why isn't this working anymore questions", you would be happier if you didn't have to, or at least had fewer. Anyways, thanks for all the hard work (on this and your other plugins)!

I'm using BracketHighlighter and it's great! However there are 2 problems I couldn't solve. 1) I'd like to make bracket bold when highlighted, so far I have foreground key in my colour scheme, but fontStyle key won't work.2) Highlighting is fast when I move my cursor line by line, but when I move it without release and then stop, it takes about a second to make highlight.I tried editing the plugin core, but with no success. Are there any settings for that?

1. This is a limitation in Sublime Text2. At most, it should be about half a second at most. Basically a match is requested on certain events like: when you move your cursor, when you edit, etc. But doing this can bog down the editor if it was actually done on every key press etc. So there is a system in place, for instance, when you are having a lot of key press events, BH will hold off on matching the brackets until the events slow down. So on these occasions when BH has entered into a mode where it is delaying the matching, you can get a delay when coming out of it. This is much better than the alternative.

1. Make the Highlight Style syntax specific? E.g. I would like the style for a bracket to be "solid" when working on a LaTeX file, but "underline" (or default) otherwise.2. Get the highlight to essentially just change the colour of the bracket? Right now I am approximating this behaviour by enabling "solid" highlight style and setting the background colour of brackethighlighter.curly in my colour scheme file to match the background colour of the colour scheme.

cOrange wrote:1. Make the Highlight Style syntax specific? E.g. I would like the style for a bracket to be "solid" when working on a LaTeX file, but "underline" (or default) otherwise.

Not currently. It would make the definitions a lot more complicated (more than they already are), but I won't rule it out.

cOrange wrote:2. Get the highlight to essentially just change the colour of the bracket? Right now I am approximating this behaviour by enabling "solid" highlight style and setting the background colour of brackethighlighter.curly in my colour scheme file to match the background colour of the colour scheme.

Doesn't really work. This is a limitation of the Sublime API. I have tried setting the background to match the syntax background and tried changing font color to try and simulate the effect, but it just doesn't work well with sublime. Sorry. If this ever changes in the sublime API moving forward, then I will gladly add the feature.