You click the issue link which takes you here: https://github.com/facelessuser/BracketHighlighter/issues.
Then you click the New Issue
button.
I don’t care who you blame it on. I’ve been very patient, and I want to bring your attention to the fact that this plugin was created in my free time, I wrote the documents in my free time, and support is offered in my free time. I don’t make money off this, and I don’t owe anyone support…or frankly anything, but I offer support anyways, and the only thing I ask is for people to be courteous and kind.
I require everyone to send their issues through the issue tracker. I want people to follow the issue template, and I want people to do their part in trying to understand because my free time is important to me. I’ve already explained in great details multiple times how to approach this in the docs and in issues. I’ve had people help out by creating pull requests to better clarify parts they didn’t initially understand. And I have no problems explaining points that people are having a hard time understanding. I do not claim the docs are perfect (I’m doing the best I can), and I am open to corrections and clarifications via pull requests.
There are numerous people who have asked questions about creating/modifying colors of brackets. If you do a search on issues, you will find some of them: https://github.com/facelessuser/BracketHighlighter/issues?utf8=✓&q=highlight%20color.
It may be a convoluted system, but I am limited by Sublime Text’s API regarding highlight regions. You have to define scopes, and the scopes have to be in your color scheme file. If people think there is a better approach to all this, I am open, but the current method for changing brackets are outlined in the documents.
I have answered and re-answered this question multiple times which is why I am pointing you to the docs (specifically here http://facelessuser.github.io/BracketHighlighter/customize/#configuring-highlight-style, where I explain it) and issues (where I re-explain it and guide people through their misunderstandings).
When you create your issue please specify exactly what part of the my multiple explanations you don’t understand. I don’t plan on typing up a whole new doc when I already have one that explains it. I will clarify any part that you are having troubles with if you can explain what you are having issues understanding.