I presume you mean VS code using differing colours for each nesting level of braces. I also happen to use VS, but you can't expect that contributors to one project will be aware of the features of others apps, you need to describe the feature you want.
You are correct and thanks for the heads up.
Without seeing your code, can't tell, you point to the VScode plugin, but not yours ;-)
That was because my code at the time was too embarrassing to release publicly 😅 I currently have my code hosted here: https://github.com/asifamin13/bracket-colors . Admittedly it's very minimal and currently bare on documentation and builds with a simple cmake setup. I plan to add the autotools build and docs later this week
Over the U.S. holiday break I decided to take a crack at writing the plugin. I used your idea of using timers to handle massive files, I think it performs pretty well. I didn't even have to use "a recursive descent parser to build an abstract syntax tree" like what VSCode does. The scintilla SCI_BRACEMATCH was enough and is also language agnostic. My plugin also handles coloring parentheses, braces, and angle brackets on dark and light backgrounds. I'd like to make the colors user configurable at some point
A few questions
- I use 3 indicators to render colored text. From the scintilla documentation, there are only 43 indicators available to use. Currently I use INDICATOR_IME - 3 as my start index, the rationale being I don't know what INDICATOR_IME is used for and it doesn't seem to affect anything. Is there a better way to choose my start indicator?
- The tricky part when writing this was determining when a bracket was inside a string, docstring, etc. The way I solved it was to check the style of the text and see if it matched up with known styles I got from trial and error: static const std::set<int> sIgnoreStyles { 1, 2, 3, 4, 6, 7, 9 } There must a better way to do this, does there exist a notion of "geany comment styles" I can leverage?
Thanks,
Asif Amin