I explain this in the settings file.
[pre=#151515] // “default” and “unmatched” styles are special
// styles. If they are not defined here,
// they will be generated internally with
// internal defaults.
// "default" style defines attributes that
// will be used for any style that does not
// explicitly define that attribute. So if
// a style does not define a color, it will
// use the color from the "default" style.
"default": {
"icon": "dot",
"color": "brackethighlighter.default",
"style": "underline"
},[/pre]
If you do not define the default style I define one internally.
Attributes from “default” is what gets used when you don’t define an attribute in another style. So in your example, you did not define an icon, so the default one got used. But you also did not define a default style, so the plugin used the internal one which defines the icon as “dot”.
I don’t understand what you are expressing here. See the above response which explains the behavior. It is acting as intended.
[quote=“Gnintendo”]
On a side note, I guess there’s no easy way to simply grab the coloring of the outermost character highlighted/underlined/outlined/etc to use. Oh well. [/quote]
It could be done, but it causes a lot more complexity to an already complex set of rules. Take a look at the actual code, you will see to make it as configurable as it is now, there is quite a bit of complexity. What you propose would require yet another exception, and impact a lot of code. It would require me to dynamically create a region for each individual bracket opposed to bracket groups as it is done now. And if I added it, someone would then not be satisfied that it picks the first scope, but want maybe the last scope etc…I don’t want to open that box. But I do appreciate the feedback. Certain features I push back on because I have to maintain this code, so no offense .