Closed SomedudeX closed 7 months ago
Should BracketHighliter be working around LSP or LSP working around BracketHighlighter? Should special exceptions be be made for every plugin conflict? I'm not even sure how I can sequence these to not be broken by LSP.
Since I was able to produce the expected behavior by installing and enabling BracketHighlighter after LSP has loaded, I was wondering whether BracketHighlighter could be loaded in later so that its visual effects won't get overridden by other plugins (is that possible? i am not familiar with sublime text plugins) . However, I would understand if supporting other plugins is out of the scope of this repository.
You can really schedule when your plugin gets loaded. The only way is to change your name to be later in the alphabet, then I'm fighting with various plugins changing their name to load later. It isn't practical.
I see, thanks for the info
I'll try something else to fix this issue then.
Description
When using the Sublime-LSP Plugin with semantic highlighting, most of the bracket highlighting styles in BracketHighlighter will sometimes be partially or fully covered by the semantic highlighting background.
Expected behavior:
Actual behavior:
Explanation: In the expected behavior, every bracket is fully highlighted with a complete outline. In the actual behavior, either some part of the bracket highlight (e.g. the outline) or sometimes the entirety of the bracket is obscured.
Steps to reproduce
Support Info